Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
rename rest-front/backend to website #2747
Related to the documentation:
As it is said
I am using Ubuntu 16.06 by myself. The problem appears while installing CppCMS. I tried to install it manually, so to download from the repository, untar, execute cmake and make in the build folder.
As a result I couldn't install CppCMS becuase I had errors during make command. After investigating I figured it out, that it is recommended to have gcc and g++ compilers of version up to 4.3 but Ubuntu 16.06 doesn't support this version and I couldn't install the older versions of gcc and g++, so the minimal version, that I could install was 4.7. Anyway, the cppcms package didn't want to compile and as a result I can not start compile the libelektra with the following command:
It reported me, that the CppCMS package does not exist.
So as a result, I suppose it is not possible to install all those dependencies for the Shared Snippets on the latest Ubuntu versions.
Thank you for the bug report. As far as I can tell from the nightly build report of CppCMS, it looks like building the framework with
And as a result there is long list of errors like the specific symbol or variable was not declared in this scope
But I see, that cppcms, that you sent me, is from other repository. I tried to download it from the official website. I will try later today with the code from the github you specified and will let you know the result.
Thank you for reporting this problem! Cppcms is an external tool, this bug should be reported to
But as already written by EMail, I think you actually want elektrad and not the snippet sharing. Elektrad "only" needs nodejs/npm, so it should be easy to run it.
I updated the docu to clarify the differences in 9c3ba98
What we actually should do is to move "rest-backend" and "rest-frontend" to a folder "website". Then people might be less likely to confuse it as a REST service that provides a get/set interface of configuration (which it is not, it is to share snippets).
@Namoshek do you think we can simply move these folders? Or do you remember potential problems we will face then?
Not sure. I think we designed the CMake build in a way that will survive a folder move. The grunt tasks are based on a configuration that is generated from CMake.