Setting up dev env in PHPStorm
This command should let compose skip that requirement.
Let me try again on my Windows
Took 5 minutes but finished with red.
Can you try delete the generated appwrite-dev image and do this steps https://github.com/appwrite/appwrite/blob/master/CONTRIBUTING.md#setup-from-source again?
I'll also try to reclone the project.
I'll redo it from the top
@Binyamin I think I got it done.
So how do I now see the Appwrite client in my browser?
If it's up and running just go to http://localhost
okay, i thought it was at some port other than 80 or something
so if i make a change either to the backend php code or the frontend svelte code, how can i propagate that change into the container?
This is also Steven, haven't done that yet.
So you mean I have to develop blind without any feedback? This is impossible.
STEVEN
What is this
There's probably solution I just never done that
Okay, thanks for your help, I'll try to figure something out. 🙂
if you made changes to the backend php code. docker compose restart appwrite would reflect those changes
This is what I've done Is this is the only way?
Because Swoole won't reload the loaded PHP files?
It works for me all the time by this command😅
If it doesn't, shutting them down, docker compose build then starting them up do the trick
Thank you both @Binyamin and @Maniac_Fighter for your help, I hope others will find this thread useful in the future.
right, swoole loads the code into memory on startup so changing the code after has no effect.
I also restart the container to apply changes
for the front end, i think most people run the dev server locally and just make sure to point the endpoint to the running backend.
My approach isn't as good for fast iteration because i mount the build output into appwrite:
$ ls -la console
lrwxr-xr-x 1 steven staff 17B Nov 23 16:52 console -> app/console/build
and then:
- modify the console code in my local appwrite repo
- run
npm run buildto rebuild the Console - restart appwrite
