New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write "Deploying Neos" #15
Projects
Comments
I would add Flownative Beach. Also there is a discuss forum post to vollect infos from. |
kdambekalns
added a commit
to kdambekalns/flow-development-collection
that referenced
this issue
Dec 4, 2018
This removes empty parts of the documentation, they are to be written following their respective tickets: - File Monitoring, neos/documentation#20 - Logging and Debugging, neos/documentation#18 - Testing, neos/documentation#17 - Deployment and Administration, neos/documentation#15 The part numbering was kept as is, to not break links. The "Deployment and Administration" part can be put back as "Part IV" when actually being written. Resolves neos/documentation#1
neos-bot
pushed a commit
to neos/flow
that referenced
this issue
Dec 5, 2018
This removes empty parts of the documentation, they are to be written following their respective tickets: - File Monitoring, neos/documentation#20 - Logging and Debugging, neos/documentation#18 - Testing, neos/documentation#17 - Deployment and Administration, neos/documentation#15 The part numbering was kept as is, to not break links. The "Deployment and Administration" part can be put back as "Part IV" when actually being written. Resolves neos/documentation#1
We've got severaly basic ways to start with Neos so this can be closed now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
...to a shared hoster, using git
...to a custom server, using Surf
...more?
The text was updated successfully, but these errors were encountered: