If you are serving static sites, you do not want to use web2py to serve the files but should instead configure the front end web server (e.g., Nginx) to serve the files directly. In that case, though, there is no particular reason the files need to go inside the /static folder of a web2py app -- you can put them anywhere on the filesystem.
Anthony On Sunday, October 21, 2018 at 9:22:05 AM UTC-4, Jaime Sempere wrote: > > Hello to everyone, > > I need some tips of how to approach a new project that I want to develop. > > I would like to build a static generator, every user would be able to > build his/her own blog using my CMS built with web2py. > > I would plan to build static pages and leaving them on static/ folder. > Maybe every user could have his own folder inside of static, like: > > static/username/index > static/username/category/ > static/username/page/ > static/username/title-of-post-1 > > and so on... (maybe I could split in subfolders starting by username first > letter -for not hitting max folders limit in a possible future, like: > > static/a/alessandro/index > /category > /page > > > Every user should be able to use his own custom domain and point to his > own folder. > > I mean: johndoe.com/index should point to static/j/johndoe/index > > > How could I achieve these requirements with web2py? Could you point me a > little to this? Also, I always mess with CNAME, ALIAS registers, and so > on... what kind of registers should I need? Would I need to create > registers for every user? Which kind? > > Thanks a lot, I really need some tips here. > > Jaime > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
