This is my first time asking a question on here, but I've been racking my brain on this issue and at this point, I have no idea what I'm missing or doing wrong.
I am currently trying to deploy my portfolio built with gulp to gh-pages. However, when I type "npm run gulp deploy", I get an error message that says "Cannot read property '0' of null". I'm assuming there's an error with my path for the deploy task in my gulpfile.js, but in every example I have seen for doing so "./dist/**/*" has been used with no error, so I'm not sure why my code isn't working in this case.
gulp.task('deploy', function () {
return gulp.src("./dist/**/*")
.pipe(deploy({
remoteUrl: "https://github.com/Picke1id/idp-responsive-portfolio.git",
branch: "master"
}))
});
Thus far, I have downloaded gulp-gh-pages to my package.json, I included the deploy task in my gulpfile.js, and I created a dist folder for production (I originally had it in my .gitignore, but I tried removing it so I could add it to my repo to see if that changed anything, but it didn't).
My repo is here https://github.com/Picke1id/idp-responsive-portfolio. I will say that I am using a new css framework called CodyHouse that also utilizes gulp. Not sure if it is interfering with the deployment, but it's worth mentioning. Any help with this would be helpful and greatly appreciated.
Related
Working on a 3d globe using threejs, I have the deployment running on GitHub pages, I had to install vite.js to facilitate the use of importing .glsl files for 3d stuff, after installing vite and trying to run GitHub pages I get the error "Canceling since a higher priority waiting request for 'pages build and deployment # main' exists" and every git push I have made after that has resulted in the error "docker pull failed with exit code 1" what does this mean?
the first screenshot is the list of failed deployments to GitHub pages.
the middle screenshot is the initial error.
the last screenshot is the error I've been getting ever since the initial one.
I have even made a new repository and still getting the same error which makes me think not has nothing to do with vite but something is wrong with GitHub.
Any advice would be appreciated.
I'm struggling to get a Google sample working.
I think I'm following the instructions correctly but now, when testing (in project-y), I receive a warning:
You are testing the Actions that you have created in project: project-x
I had previously used project-x but it has since been deleted. I've tried deleting the project and recreating, redeploy etc. but I'm entirely unable to avoid the error.
I'm unable to determine where project-y references project-x and how to correct this.
The only location where project-[x|y] are referenced is in ./sdk/setting/setting.yaml:
defaultLocale: en
localizedSettings:
developerEmail:
developerName:
displayName: Updates sample
fullDescription:
privacyPolicyUrl:
pronunciation: Updates sample
shortDescription:
smallLogoImage:
termsOfServiceUrl:
projectId: project-y
When I gactions push and gactions preview deploy, both commands correctly reference project-y and the generated URLs correctly point to project-y:
gactions push
Pushing files in the project "project-y" to Actions Console. This may take a few minutes.
Sending configuration files...
gactions deploy preview
Deploying files in the project "project-y" to Actions Console for preview. This may take a few minutes.
Sending configuration files...
I've scoured the gactions config and the cloned directory for hidden configuration files but am unable to find any references to project-x.
If I search, the only reference I find is the single reference to project-y in the above YAML.
I have seen the same issue.
In my case, it is because I used the same Display name for project-x and project-y.
I hope you check your project's Display name on Develop tab in Actions Console and solve your issue.
I have been creating this website for a few weeks now (I am fairly new to web-dev) and have just recently made a repo (on Github) for it.
Link:
https://github.com/Lathryx/TopShelf-Recipes
I want to deploy with Netlify however I am unable to. Netlify continuously gives a 404 error on the site(s) that I create. I think it has something to do with the publish directory but I'm not sure. I want it to open to landing.html.
The few times I have tried to deploy now I have tried:
No build command/publish directory.
No build command and the publish directory set to TopShelf Recipes
(have also tried /TopShelf Recipes).
No build command and the publish directory set to TopShelf Recipes/landing.html.
No build command and the publish directory set to /TopShelf Recipes/landing.
Image of Error:
I really don't know what to do. Does anybody know why this is happening?
The netlify/my-first-netlify-deploys demo project shows files with a netlify.toml to adtually generates the files.
Result: https://playwith.netlify.app/
But if there are no generation involved, then said files should be directly at the root folder of the repository, not in a subfolder.
The landing page of your site must be titled index.html (as I’ve found), this fixed it for me. Mine (originally) was titled landing.html.
I will keep this in mind in the future.
I am working on a project with multiple people, a website application which requires webpack to be built, uglified, concatenated into a few files e.g. app.min.js, style.min.css etc. - As a result of this, in an effort to prevent merge conflicts we recently added the build folder to .gitignore, under the assumption that we would be able to build during deployment.
When pushing to the Master branch, we automatically "deploy" through Semaphore CI (similar to Travis) which runs composer install, npm install, and finally "npm run build" which triggers the webpack build. This is all built and then tested on the CI side of things, and then Semaphore automatically deploys to Amazon's Elastic Beanstalk where our application is hosted.
The problem with this is, it seems Semaphore doesn't upload the build it's just tested, but rather the Master branch itself which has no built JS or CSS. I'm wondering if there's a way to push these built files to deployment as well, or if running the entire build process AGAIN on Elastic Beanstalk is the only route. It seems unnecessary to have to do that process essentially 3 times, locally, CI, and then deployment. Every time a step like this is needed on EB the actual re-instantiation time gets longer, which I'd like to keep as short as possible.
Obviously if building it a 3rd time on EB is the only way to go about this then I'll have to, just wondering if there are better solutions for this whole workflow.
I haven't worked with Semaphore CI, but you might be able to use an .ebignore file.
If you create one, the cli will use that instead of your .gitignore file.
I find in some deployment situations you want the inverse of your .gitignore (all compiled, no src). It essentially lets you pick the files from your project directory that you want to deploy, in the same way as the .gitignore file.
Edit: I just noticed the documentation on aws is lacking. It only mentions file exclusion, but you can include files too.
Edit 2: I don't think Semaphore supports the use of .ebignore, so right now this solution isn't of any use. :(
I just had a great first experience with https://deploybot.com/. The can deploy directly to elastic beanstalk. It might be interesting or you.
So, I have a webapp I am creating using the 3 muskateers yeoman, grunt and bower.
My questions are:
What is best practice when it comes to uploading my webapp into a git/mercurial repo? Do I include the entire project? What about directories like 'node_modules' or 'test', etc?
Also, when deploying to live production site: Will my 'dist' folder be what I should be uploading?
With research yielding no results (I could be searching the wrong things?).. I'm a bit new to this process so any feedback is greatly appreciated. Thanks!
You should always commit all of your yeoman, grunt, and bower config files.
There are two schools of thought on committing the output they produce or dependencies they download:
One is, you should upload everything needed for another user to deploy the web app after cloning the repository, without performing any additional operations. The idea is, dependencies may not exist anymore, network connections might be down, etc.
Another is, keep the repository small and don't commit node_modules, etc, since they can be downloaded by the user.
As far as the dist folder goes, yes you'll be uploading it to your server, as it contains all of your minified files. Whether or not you want to commit it to the repository is a separate question. You might let the user build every time, assuming they can get all the dependencies one way or another (from above choice). Or you might want to commit it to tag it with a release version along with your source code.
There's some more discussion on this here: http://addyosmani.com/blog/checking-in-front-end-dependencies/