Can someone tell me how I can deploy (=put in production) my local VuePress site?
If I correctly understand https://vuepress.vuejs.org/guide/deploy.html, we can't deploy VuePress on our shared host?
If this is true, are there alternatives like using a tool to "convert" the VuePress site to a static site?
Thanks a lot!
Christophe
So simple...
By running npm run build, we get a folder called .vuepress\dist where everything has been converted to .html files.
We just need to copy all these files onto our FTP folder and tadaaa...
Damned, why I hadn't seen that.
Maybe this one?
https://github.com/jenkey2011/vuepress-deploy
A GitHub Action to build and deploy Vuepress sites to GitHub Pages.And you can set a CNAME file.
Related
I have a video.mp4 file in my public folder in a NextJS app. When running Next locally (npm run dev) I can reach the file by typing localhost:3000/video.mp4 but once I push to Vercel mydomain.com/video.mp4 doesn't work. I have used Git LFS to push the video file because it was over 100mbs. I have other static files in my public folder such as images and icons and these work perfectly well in both development and production environments.
I have no clue what to do. Any ideas?
Vercel currently does not support Git LFS. We recommend hosting that video asset elsewhere.
https://vercel.com/support/articles/best-practices-for-hosting-videos-on-vercel-nextjs-mp4-gif
I started looking at the Magnolia CMS system and found a project on the web and I can't open it and run it.
This are the files:
author.tar
magnolia.tar.xz
public.tar.xz
magnolia.tar
I tried to add the files into apache folder and run it, I tried with Magnolia CLI to run it, but with no success.
I miss something, but I'm completely new to Magnolia, so I have no idea.
Thanks in advance.
These pages should be sufficient to get started.
https://documentation.magnolia-cms.com/display/DOCS56/Getting+started+with+Magnolia
If you fancy CLI, then
https://documentation.magnolia-cms.com/display/DOCS56/Magnolia+CLI
Hope that helps,
Cheers,
Probably a silly question, but I cannot find any good advice on the internet so far, so hopefully you guys have some good advice. I would like to use GIT for version control and use it to deploy changes to my websites to the server(s). It's easy when I use NodeJS, but a bit more complicated when using a CMS system, to my opinion.
When I use NodeJS
When I use NodeJS it's quite easy to have a node_modules folder which contains all the external libraries which I will install on deployment. The rest(my own files) will be saved on Github and deployed to my server if changed. Obviously I will not store the node_modules folder on my Github account or send it to my server (node modules will be installed on the server, on deployment). So it's pretty easy to keep those two (third-party an my own files) seperated.
When I use Wordpress, Magento or something similar
Now it gets complicated. Mostly because CMS systems like Wordpress have a folder structure like wp_content/themes/theme_name/, so your own theme files are more or less entangled with the core structure, instead of separated like NodeJS. And it doesn't seem right to commit all my core files to my Github account as well or send all those core files to my server on every deploy (I would prefer to install them using composer or something, serverside), because I'll never touch the core files, obviously.
So is there any advice? Is there a better whey to handle this? Maybe change a configuration file with the path to my theme folder or something?
The best way to do this is to move your wp-content folder outside of your standard installation. I tend to have a folder called "wp" with the basic WordPress installation in it and a folder called "wp-content" at the same level for my content files. You can then tell WordPress that your content folder is elsewhere with the following:
define('WP_CONTENT_DIR', dirname(__FILE__) . '/content');
That goes into wp-content.php which you can also take out of the main WordPress install (and thus add to git) and place at the same level as your folders.
To make things even better consider looking at composer https://getcomposer.org/ and using that to bring in WordPress core and plugins https://wpackagist.org/ is your friend here. This guide got me started on using composer with WordPress and its a good start https://roots.io/using-composer-with-wordpress/ you can pull in your theme from git as well via composer which is great for when you deploy etc... Capistrano for example can run composer on a server :)
Ok I'm new to Polymer, after seeing the main page and Google IO 2016 video, I wanted to try it out, and right now I created a basic web application with it.
I managed to get it build and running it through the "polymer serve" command, but now that I want to release it to a production environment (I have an nginx cluster), how do I build the application to just a bunch of static website files?
I executed "polymer build" and I see the build folder and it contains 2 folders: bundled and unbundled, and inside them there are the bower_components, src and test folders as well as other stuff for running it through "polymer serve" but there's not a build/dist of build/static folder that I can copy into nginx so the application is served through it.
BTW, what I mean about a dist folder is without a readme, bower.json, test, bower_components, etc. just the pure needed HTML, CSS, JS, etc files that need to be served through nginx (or any other web server) as static file web content.
I went through the documentation but there's no details on how to do such task.
Any suggestions on how to build a static content folder for serving my polymer web app through nginx?
Thanks!
As of Polymer-CLI v0.11.0, there's no built-in way to filter out files from the bundle, but it's a requested feature. Also, the build output currently includes extraneous files (a bug), such as the test directory.
As an alternative, you could use Polymer Starter Kit 1.3.0, whose dist folder doesn't include the extra files (although it does include required bower_components as-is).
I currently have my resources (images) in ...
C:\inetpub\wwwroot\images
I also have the images in the same location on my production server. How can I set it up so that I don't have to constantly sync up the folders? Seems like an easy thing but I'm not sure...
Any other information let me know and I will provide. Thanks!
Why don't you include them in your web project? That way when you deploy the web project the images are included by default :)
You can also use one of SCM's such as SVN or GIT to keep files in sync, if you don't want each time redeploy your application. But you should "checkout" to synchronize files or make a .bat file which will do that automatically.