Improving to First Run #78
Replies: 4 comments
-
re
Aside: ShellCheck can be great for warning when using syntax not widely available. Not sure how secure that key needs to be, maybe can borrow from some other popular shell scripts, but can't think of what those would be right now.... Perl should be a bit more ubiquitous. Could do a architecture check/switch statement and use preferred built-in password generators? I dunno - I try to avoid security, datetime and language encodings in my software development life and somehow getting away with it :D |
Beta Was this translation helpful? Give feedback.
-
I think the idea of having a deployment to Netlify/Vercel/Render et. al. would be very useful to those who’d rather not admin their own server, myself being one of them. |
Beta Was this translation helpful? Give feedback.
-
I'm trying to package the current docker implementation into a cloudron package (docker based) |
Beta Was this translation helpful? Give feedback.
-
Oh nice! Let me know if there’s anything I can answer that may help!
… On Nov 8, 2021, at 19:51, Ricardo ***@***.***> wrote:
I'm trying to package the current docker implementation into a cloudron package (docker based)
but there are several parts of the deploy that I'm not sure how to implement in the cloudron context, still exploring :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Beta Was this translation helpful? Give feedback.
-
Once you get Tanzawa running, the first run experience is lacking. Eventually it'd be great to have a nice polished workflow, but I think just the basics should suffice for now.
There's two (or three) pain points:
Running Tanzawa in Development
I don't think it's that bad at the moment. Running a Docker container to standardize Python/Geo libraries is super helpful. Manually running the dev server from within the container is less than idea. Maybe this could be improved to always run the dev server on boot?
Deploying Tanzawa
Deploying Python applications in general is a complex process. Providing a production Docker container (running gunicorn) and instructions for Ubuntu (systemd) is good for those running their own servers. Maybe provide 1-click deploys to Digital Ocean? Can we lower the barrier to entry and do Heroku/Vercel/ other PaaS?
Initial Setup
I've started on a PR ( #74) to help address some of the pain points of initial setup.
In the current install instructions, you register your account via the command line. That's not great. What I'd like to do is, if no users are registered to redirect to a First Run page / workflow. On this page users could input their username / email / blog name. Perhaps a second step modify Streams? After that's complete, perhaps a link to write your first post or Import from Wordpress? ( Sidebar: Wordpress import exists at
/a/wordpress/upload/
but I've only tested it with my personal blog, so it may not work perfectly )Beta Was this translation helpful? Give feedback.
All reactions