From e87d78a0555a232ad271c87ad2fb5f8a3560f577 Mon Sep 17 00:00:00 2001 From: CherrelleTucker <106271365+CherrelleTucker@users.noreply.github.com> Date: Wed, 15 May 2024 12:05:05 -0500 Subject: [PATCH] older/newer --- _posts/Implementation/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/Implementation/index.html b/_posts/Implementation/index.html index b24f486..f39d4c0 100644 --- a/_posts/Implementation/index.html +++ b/_posts/Implementation/index.html @@ -8,4 +8,4 @@
$ bundle lock --add-platform x86_64-linux
Next, configure the Pages service.
Browse to your repository on GitHub. Select the tab Settings, then click Pages in the left navigation bar. Then, in the Source section (under Build and deployment), select GitHub Actions from the dropdown menu.
Push any commits to GitHub to trigger the Actions workflow. In the Actions tab of your repository, you should see the workflow Build and Deploy running. Once the build is complete and successful, the site will be deployed automatically.
At this point, you can go to the URL indicated by GitHub to access your site.
On self-hosted servers, you cannot enjoy the convenience of GitHub Actions. Therefore, you should build the site on your local machine and then upload the site files to the server.
Go to the root of the source project, and build your site as follows:
1
$ JEKYLL_ENV=production bundle exec jekyll b
-
Unless you specified the output path, the generated site files will be placed in folder _site
of the project’s root directory. Now you should upload those files to the target server.
Unless you specified the output path, the generated site files will be placed in folder _site
of the project’s root directory. Now you should upload those files to the target server.