-
Notifications
You must be signed in to change notification settings - Fork 0
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
Compatibility issues between vue.js and GitHub Pages. (Unbuilt static pages) #11
Comments
Would like to see a 👍 if you approve of the |
Got it, I can also help with documenting front end stuff |
👍 gc (google cloud) does this, no prob for |
its not like im saying to use gc |
Right, the |
@apap04 im not gonna fucking use google cloud |
oh. ok |
reee |
ima make a dev branch and a build branch |
no dont wtf |
we don't need them and why would we make em? |
re e e e e |
You can only have one github pages site per repo |
No one will accidentally merge, we have version control in the gh-pages branch, we'll rollback and disband the version. |
hopefully no one will accompany merge. im directing that to you, bin ;) |
No one can merge other than you and me LOL. |
BRB gonna merge :^) |
ok maybe u too |
It's joke |
but still ;) |
at this point, we should create this issue again. |
I know what's up. We're ignoring modules from github for it to work properly. |
The current build sitting in the master branch at the moment is not compatible with vue.js; we need to separate a branch for debugging releases launched on GitHub Pages.
All debug-deploy (staging) testing and applications are to be deployed to the
gh-pages
branch. After a build of the static files, throw in a PR, and we'll merge into a folder. Examples:staging.otako.moe/1.01/index.html
The static files pulled with your version will be thrown into a version folder (along with a
creator_info.json
andCREATORINFO.md
file).Anything on this repository's
gh-pages
branch will be accessible over the internet usingstaging.otako.moe
where staging shows that this is an indev open source product. The default index.html file will automatically redirect the user to the latest version of our staging.If needed, we'll create a simple script to update our staging frontend every time the master branch is updated.
I'd like to request that @prydt builds version
0.01
of Otako's staging and open's a PR togh-pages
. @apap04 and I will take care of merges.Also yes, we're moving this to
staging.otako.moe
instead ofotako.moe
. Our deployed frontend (otako.moe
) will be hosted and served statically either fromThis topic is still undergoing discussion, we'll post more in the README.md file if needed.
That's all this issue has to say, if anyone's wondering, Otako's documentation and specs will be released alongside the otako.docs repo explaining how this will work, and how front-end developers can get started with the webpack version of otako.js.
~bin
The text was updated successfully, but these errors were encountered: