3 ms·
I got it running locally like this, using uv to manage dependencies: git clone https://github.com/redimp/otterwiki.git cd otterwiki mkdir -p app-d
by simonw 2y ago
I got it running locally like this, using uv to manage dependencies:
git clone https://github.com/redimp/otterwiki.git
cd otterwiki
mkdir -p app-data/repository
git init app-data/repository
echo "REPOSITORY='${PWD}/app-data/repository'" >> settings.cfg
echo "SQLALCHEMY_DATABASE_URI='sqlite:///${PWD}/app-data/db.sqlite'" >> settings.cfg
echo "SECRET_KEY='$(echo $RANDOM | md5sum | head -c 16)'" >> settings.cfg
export OTTERWIKI_SETTINGS=$PWD/settings.cfg
uv run --with gunicorn gunicorn --bind 127.0.0.1:8080 otterwiki.server:app
I filed an issue here suggesting that for the docs https://github.com/redimp/otterwiki/issues/146 https://github.com/redimp/otterwiki/issues/146 - and also that it would be great if getting started could be as simple as this:
pip install otterwiki
otterwiki \
--repository app-data/repository \
--sqlite app-data/db.sqlite \
--secret-key secret1 \
--port 8080
- oarsinsync 2y agoAnd to think people used to think ./configure —-prefix=/home/user/appname make make install was too complicated
- emj 2y agoThe problems was mainly that even "apt-get build-dep" is not enough to handle all the problems that arise from that. Even if configure was standardized, there was always problems with diversity in systems. The NIH syndrome is still big in software build tools, everything is complicated unless you have written it yourself in your environment. Admitted I seldom run those commands manually anymore, but things have gotten way worse when I do try. Specific versions of tools, libraries and kernels, or just kernels. Nix build scripts are actually one of the worst offenders here often ignoring every other standard available. Not saying it is bad, just an example of why what you write above is more complicated than it sounds.
- rcarmo 2y agoI got it to work under Piku (https://piku.github.io https://piku.github.io) in much the same way (since I support uwsgi, that bit was trivial). I did have to hardcode the data path, and I think having some form of export/snapshot would help as well, but submitting a patch might be a fun weekend project.