search

aurelia-ui-toolkits / carmel-fe

Carmel editor front end application
MIT License
1 stars 1 forks source link

Deploying aurelia applications #20

Open adriatic opened 7 years ago

adriatic commented 7 years ago

Deploying to gh-pages

Using the Github pages basic documents with this assumption:

Enabling GitHub Pages to publish your site from master branch.

Note that I am retaining the title Enabling GitHub Pages, despite the decision not to use gh-pages branch - as using master seems lot more convenient.

Initial setup

Defined by this screenshot, indicating that I think we should host all of our new applications (starting with Carmel-fe, which will have the name ce (for catalog editor) in the aurelia-tools organization image

adriatic commented 7 years ago

Simplest possible sample

The repo has a single index.html file

<!DOCTYPE html
<HTML>
   <HEAD>
      <TITLE>
         A Small Hello 
      </TITLE>
   </HEAD>
<BODY>
   <H1>Hi</H1>
   <P>This is very minimal "hello world" HTML document, hosted at https://aurelia-tools.github.io/deploy/</P> 
</BODY>
</HTML

which is pushed to the master as

H:\work\aurelia-tools\deploy (master)
λ git push
Counting objects: 3, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 377 bytes | 0 bytes/s, done.
Total 3 (delta 1), reused 0 (delta 0)
remote: Resolving deltas: 100% (1/1), completed with 1 local object.
To https://github.com/aurelia-tools/deploy.git
   643053d..494b65b  master -> master

resulting with: image

adriatic commented 7 years ago

More elaborate sample

Replacing the content of the H:\work\aurelia-tools\deploy (master) folder with the unbundled content of the dist folder of the skeleton esnext application. (see this article for details.