Alex Harsanyi writes:
>> Although it's not exactly the same thing, I use `info.rkt'[1][2] >> (similar to `setup.py') for this purpose and each one of >> my web apps is its own package. >> > > Does this mean that the application itself is available as a package and > you can require files from inside the application from another program? Yes. In fact, I leverage this property to keep my apps' tests in a separate package. My e-commerce site, for example, is composed of two packages: `matchacha' and `matchacha-tests'. This means I don't have to ship my tests and their dependencies to the server and it also has the added benefit that compilation times are improved. The latter is important in development since my development server watches the FS and it recompiles any files that change before it restarts the server. > More importantly, can you have two copies of the application installed on > your system, for example for development purposes? On my local machine, I only have the application installed once and it is linked to my local git checkout. I think that if you try to install the same package under multiple names, `raco pkg' will complain. I can't imagine wanting to have the same application installed multiple times for development, though, so I don't think I fully grasp your question. On my production server, I run the binaries as two separate systemd services: one for production and another one[1] that I use to test releases before they go out. Since I only ship distributions to the production server, I don't need to install any packages. In fact, I don't even have Racket installed on the production server. [1]: https://sandbox.matchacha.ro/ -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/m2muf48tna.fsf%40192.168.0.139.
