Closed relativityboy closed 6 years ago
It seems like all of the existing documentation on how to do this is just out-of-date. So I took a step back and looked at other options. I've had some luck with this:
steemit/devportal
repo to inertia186/devportal
.jekyll build
mv _site docs
git add -A
git commit -a -m "manual build"
git push
gh-pages
but instead use master/docs
.Looking at the api-definitions, they appear to have neatjson formats, but the CSS is messed up. I have high confidance that this will work in production.
2. jekyll build --destination docs
d1f65d2f09699f40460039e91352209a63d17578
Hrm. I'm not a fan without practice changes. I don't like us using a dir in master as our built code, not while we're using master as our "integration" branch. I want our .gitignore for most branches to include the deploy folder.
To proceed I suggest we move our default branch to be something like develop
.... we branch and merge our issues on that, and merge develop
into master only when it's time to release.
@inertia186 @feruzm @roboza. - input please.
I think our hands are tied, somewhat, because github doesn't allow very many options for where pages are published. I agree with your suggestion.
I am good with the idea of a develop/staging branch and then when we are ready merge to master which will be "live" but as @inertia186 said, We will have to build outside of Github since they will not allow custom plugins. Not sure if we can get away without deploying to a folder in master.
I don't mind also using develop
instead of master
and merge only when there is a release
Results: I think the root cause of the #116 failure was that GitHub pages do not work the way most google searches lead one to believe. There may have been a time when a merging gh-pages
with an existing _site
already present did not kick off a new build. But I can imagine a scenario where people inadvertently include _site
and wonder why it isn't doing a new build, and that was probably more common than people who wanted to do their own build.
I recommend switching todevelop
to merge issues and master
/docs
for release.
I think we have a plan. I'll switch the default branch to develop
and set the site to follow master
We want to be able to deploy our site with jekyll modules that are not supported by the gh-pages build process. The code created by #116 was intended to address this, but the gh build did not function as intended. We want to know why.
AC
master
andgh-pages
branches such that we are able to run a rake task conforming to the requirements outlined in #116