I just finished making an ember project (super simple nothing huge)
You can check it out <here>
but I am trying to deploy it to make it into a website on github pages and there is hardly any documentation out there and was wondering if I could get some help. Thank you
There are three strategies to do so these days:
Ember CLI Deploy is a famous deployment pipeline for Ember.js applications. The ember-cli-deploy-git plugin adds support for GitHub Pages as deployment target. There is an additional plugin ember-cli-deploy-git-ci, which adds support for deployments from a CI pipeline on top of that one.
The Ember addon ember-cli-github-pages adds a command to Ember CLI, which deploys the project to GitHub Pages. It's similar to the Ember CLI Deploy pipeline but working as a standalone solution.
You can deploy to GitHub Pages from GitHub actions. There are different Actions available in GitHub Marketplace to do so. The most famous one if comparing by stars is the GitHub Pages action. To use it you would need to build your Ember project as usual and set the publish_dir option of the action to ./dist. Ember CLI stores the build output by default in that folder.
It's up to you which approach you use. All of them are common in the ecosystem. Maybe some hints to decide:
If running the CI on GitHub actions, I would recommend to also us it for deployment.
If using Ember CLI Deploy in that project already for deployment to another environment, I would recommend to use it for deployments to GitHub Pages as well.
If not using a CI at all and just looking for a quick solution, I would go with ember-cli-github-pages as this is the simplest one.
If this is a playground project and you want to learn more about the common deployment process for Ember applications, I would go with Ember CLI Deploy.
Related
The most popular boilerplate for vue/electron usage, seen here: https://github.com/SimulatedGREG/electron-vue
Is outdated, and only uses vue cli2.
The quickest, and easiest way I've found to get Vue and Electron playing nice together is vue electron-builder.
To use, set up a project with Vue CLI3 using
vue create my-project
then CD into that directory, in this case "my-project", and run
vue add electron-builder
This sets up barebones scaffolding that allows vue and electron to play nicely from the get go. You can test your work by launching an unbuilt test version using
npm run electron:serve
and, when you are ready for deployment, may use
npm run electron:build
to build. This vastly simplifies the process, seen elsewhere, of dealing with a giant over engineered boilerplate or trying to write out relative pathing so your builds and dev environments both work identically.
This repository contains the starter template for using vue-next with the latest electron.
I started to learn electron & vue by the great project electron-vue. This project is also inspired from it.
https://github.com/ci010/electron-vue-next
I'm fairly new to the React ecosystem; I've made a simple single page webpage for a tech conference and I want to deploy it to gh-pages.
I know create-react-app has very good documentation on deploying to gh-pages but my app was not made with that. I manually setup all the configurations for Webpack and React, instead of using the react-scripts module that create-react-app uses.
I tried finding some posts about deploying a non-create-react-app to gh-pages but I've had no luck so I was wondering if there's any simple solutions.
My current solution is to just push only the dist folder to the gh-pages and serve that. I wanted to see if there's a simpler way where I can just push the whole dev branch over to gh-pages and be able to serve the correct elements still.
You can push the whole dev branch and select github to display the page from master branch. Make sure that in master branch the scripts are compiled into / (index) of the repository, so your page shows up.
I know it's late on this question, but you can use gulp with gulp-gh-pages to automate pushing a React build to Github Pages.
We'r developing an app in Steroids Supersonic framework (Based on Angular designed for Native apps). The team before us added following two dependencies which giving problems when we try to install all the dependencies using bower.
"angular-ui-laicos": "git#github.com:Laicos/angular-ui-laicos.git",
"appgyver": "git#github.com:Laicos/appgyver.git",
Both of git repositories are not there, so what kind of alternative would be used for this case? In the project at many places both dependencies are being used.
I'm having an Ionic project which I need to keep in github. When you start an Ionic project it auto generates a lot of library files. Do I need to keep all those library files while pushing the project to the github repo ? Is there something similar to maven available for Ionic projects which I can make use of ?
In JavaScript projects, we tend to use npm or bower. npm is the main one used these days (certainly has the largest ecosystem) and is also the one I mainly use, but bower certainly has quite a few front-end orientated modules that you can use.
npm comes packaged with NodeJS automatically; bower will require NodeJS to function as well, but is installed separately.
I need to separate my Frontend and Backend into two different repos. Because one developer can't install rails and doesn't need it (we can make stub for API).
How can I do it in case of deployment? Do I need git submodule? How to use it (with GitHub and Ninefold)?
I found information about how to develop standalone frontend app (thanks I can use grunt) and how to use submodules, but I can't combine it. Please help! Does anyone have such experience?
Having your rails app provide a RESTful API is a good idea here. Your standalone front-end app can then interact with the API over HTTP(S).
If you want the front-end app within the rails app but need repository separation (i.e. don't want the front-end developer to access the code of the rails app), using a git submodule may work but probably needs some organisational thought.
This is what I'd do:
First clone your rails app from GitHub or Bitbucket (or git init one locally) and then configure a git submodule.
git clone git#github.com:pathto/myawesomerailsapp.git
cd myawesomerailsapp
git submodule add git#github.com:pathto/mystandalonejsapp.git app/assets/standalone
Now when you cat .gitmodules you'll notice there's a new submodule configured in your repo.
Commit and push your changes. Ninefold will detect the submodules and use them, but if you have any problems just get in touch.
Good luck!