-
-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to launch Jekyll Admin as a seperate service #681
Comments
Hello @csharpee Jekyll Admin was not built to be used as a SAAS. In fact, it was designed for layman editors and non-technical folks. I'm sorry, but your expectation is exactly opposite of what Jekyll Admin is..:
|
Hi @ashmaroli 👋 It seems I must create my own basic auth with nginx, create a simple back-end dashboard and point to api location for basic CRUD like operation using javascript. I don't want to use react or other javascript pancake framework. All I need is Jekyll with Liquid super powers. All I need is HTML, CSS and JS to create for mobile and web. I use my own GIT server with automation and also serves the static site like GitHub pages. In short, I want Jekyll to have a Jekyll authenticated dashboard that can be used for individual and multiple sites.
Currently, the Jekyll Admin plugin isn't used because devs edit the source code with a text editor like vs or atom. |
Me too buddy... me too. However, its clear thats not what this project is for! Therefor... WE FORK! I'll be meditating on this and how it can be forked to provide the functionality you've described. Currently i intend on setting up a series of dependent docker containers that will do this; but it will likely not have any use outside of my specific designs. Reach out to me directly if you would like to collaborate on this. |
Also for what its worth this project is react/redux |
Description:
Am I able to launch Jekyll Admin as an independent service without launching Jekyll serve?
Having Jekyll-Admin locally isn’t really what a ‘developer’ needs. That type of thing is for editors and non-technical web admins.
For my clientele, as of now, would have to go through my company to update posts, pages, etc... I don't expect a client to launch jekyll serve and learn git to know how to update things via the Jekyll file system.
I really want to make Jekyll Admin work. I don't want to use a JS pancake CMS.
Stupidscript https://talk.jekyllrb.com/t/jekyll-admin-rewrites-relative-asset-urls/4152 has come close to this, but all they have done is make Jekyll serve a public facing web server.
I want Jekyll Admin as an API for my CMS that less tech savvy individuals may use to update posts, pages etc...
My web UI/UX will be separate from the data and on building the _site as a developer, would automatically GET the API data before the static site is built with Jekyll. So, the API would only be used to fetch data when a developer or authenticated jekyll admin user updates the actual Jekyll repo data, rather than having that API be used when loading a webpage.
The text was updated successfully, but these errors were encountered: