= best workflows for managing (web)servers? = What are some good ways to manage running servers as part of the dev workflow? Ideally with integration into the compilation support, so that the server can be automatically restarted when the project is successfully recompiled I've found the Prodigy package so far - it seems pretty nice but doesn't address that second part as far as I can see - with Prodigy I'm responsible for manually restarting my server whenever I recompile For my (fairly similar) use case, I just hacked it all together with a mixture of bash and elisp. It goes something like this Bind key to function, Have the function rsyncthe entire project to the remote host, Have it call ssh, invoking makeon the remote host Then simply bind another key (or have the first function block if you prefer) to a similar function that ssh's into the remote host and executes the application. In your case, I expect it can run something like "sudo service apache restart" or similar instead If you've got multiple servers and/or multiple website projects, Projectile is quite competent at keeping tabs of what your current project is and where it should be rsync'ed to == About Community == Members Online Top 5% Ranked by Size