Deploy: First time (staging) setup issues

[dgrdl]

When setting up a project, the .env and web/.htaccess files (among others) are excluded from deployment by default, which leads to the need for manual setup on the server. That entails:

• creating a .env file / copying the existing from local and adjusting it
• logging into the backend via your-website.domain/wp/wp-admin and opening the permalinks page

I'm not sure if there is a nicer way, but maybe we could (optionally) deploy once after the create task has finished? This step could then take care of creating the .env file and flushing the rewrite rules.

The annoying thing would be the increase in prompts you have to go through (but you need to go through these anyways with our workflow).

[domtra]

this is purely optional to deploy to a staging server. i also do not want to have a command, that if you run it accidentally, will delete something you have set up on a remote server (could be production as well).

we could though make more use of the cli, also on staging. this way it would only work, if the .env does not exist.

my plan is to make use of wp cli more anyway. also getting rid of search-and-replace-db. but for that we have to change a couple of things and add a way to setup wp cli on a remote server if it is not present. I have some ideas, but would not prioritize them for the initial release

[bdbch]

i also do not want to have a command, that if you run it accidentally, will delete something you have set up on a remote server (could be production as well).

agree, did this once accidentally via flynt deploy with a wrong dir setup in flynt.json.

After setting up multiple flynt websites the initial setup became less and less annoying with each project.