Planet dump is supported (but it still takes about 2 days to run). It looks like this can run in the background since EXCLUSIVE lock for editing does not require the dump to stop.
I'll look in to this once I've got the server online.
Looking at whats on git at the moment I don't see an issue with
setting it up, it's all straight forward. If anything crops up
I'll let you know.
If you can continue developing what you have at the moment would
be great. Only thing I've seen that I'd look at changing to make
configurable is hard coded directories. eg in
pycrocosm/changeset/management/commands/applydiffs.py line 66
Also maybe a comment for each function as to what it's supposed
to do. Sorry I'm an old school programmer and was beaten into me
to have comment for every function. Mind you I don't always do it
and usually regret it later.
My intention is to get a new api server up and running but initially
just importing from the current api server. I'll use a similar
script to what I use on the map server to apply the minutely diffs.
Once it's stable I'll look at changing over editing similar to what was done when it was forked from osm. So new id's for new changesets/nodes/ways/relations/diffs probably beginning with 2xx....... Anything that is edited on the current api server will continue to be updated but id's will not conflict. Target July 2018.
Then by October 2018 we can turn off the current api server.
I have not seen anything from 80n on this so not sure on his thoughts on possibly changing over.
Also need to look at possibly transferring the domain name. Assuming we keep fosm.org which I suggest we do.
fosm.org could then be on the the nameservers I use.
May also look at a redesign of the main website. Possibly an
extension to map.fosm.org
I have been experimenting with pycrocosm just on my laptop at the moment.
When you have a chance could you expand on the installation steps in the README file.
I think I'm understanding it but just looking at where you are
coming from/heading with it.