Imagine for a moment that you are me: a balding smoothbrained millenial on the wrong side of 30 emanating a constant funk of mildew and sour milk. The last time you cared about coding you were booting off floppy diskettes and making HTML websites with frames.
Now, I'm working on an idiot project. I want to make a web applet where I could input text, store it in a .txt file and then retrieve it from another PC.
Is web2py and an apache server a feasible approach? I'm too for django.
web2py uses SQL for a storage db, but honestly it's going to be a single user app (just me) and storing the .txt files in a directory with a date/time naming scheme would be fine.
Would this work the way I want it to? I have tried googling but these questions are too basic and r-slurred to find answers to.
Jump in the discussion.
No email address required.
Just use flask (I think rdrama does)
Jump in the discussion.
No email address required.
This seems a lot easier. Can i build a whole butt website in flask? Does it do docker?
Jump in the discussion.
No email address required.
You can.
I would just use the built in webserver and not even bother with apache, for low volume stuff you really don't need a reverse proxy and you can always just add it later if you do.
Jump in the discussion.
No email address required.
I want the applet on the cloud but I dont understand how I would use the built in server on a cloud service. Would something like AWS run flask and I would just build the app there?
I've only ever written (read copy/pasted code) for a Twitter bot that ran off AWS
Jump in the discussion.
No email address required.
Then use whatever google appengine uses (web.py I think).
Deploying your website would be like 95% of the work on a generic cloud service, so unless you want it to be an Important Learning Experience just use appengine.
Jump in the discussion.
No email address required.
I kinda do wanna learn how to run a server and build sites and maybe even make a db, it's stuff I've been avoiding for almost two decades and I kinda wanna know it
Jump in the discussion.
No email address required.
Then my suggestion is to
1. Implement it using appengine
2. Deploy standalone at your leisure
This way there's a risk that you never finish 2, but from your self-description, it's actually less of a risk than that you get stuck with deployment hurdles and never get to writing the actual app at all!
Also, when looking at standalone kind of stuff, I'd consider Heroku. I have never actually used it myself, but apparently it's free if you give them your credit card number (and can work 50% of the time if you don't).
Jump in the discussion.
No email address required.
This is really good advice, I'll look into both of these asap
Jump in the discussion.
No email address required.
More options
Context
More options
Context
More options
Context
More options
Context
I dunno I don't use AWS but you can just use a cheap VPS and run it there. You can also run it in docker if you really want, not sure it's needed for this though.
Jump in the discussion.
No email address required.
That helps a lot! Thanks
Jump in the discussion.
No email address required.
More options
Context
More options
Context
More options
Context
More options
Context
More options
Context
More options
Context