Well I am new to hosting websites on GitHub, I tried hosting few of the basic project on GitHub and they worked very well. Basically for this project I was assigned to host a website provide by Guide and that has the index.html file present in \public\fonts\icomoon.index.html.
I still haven't tried moving the index.html in the main folder but is their any other way to do it without moving the index.html file.
Related
I developed a project in Laravel and the files are served from htdocs files in the XAMPP Server. Is there any way that i could restrict the access to htdocs. Or is there a way that the whole project would be compiled and minified so no one can see the source. (Like Angular production version).
Thanks in advance
Trying to start from Timber but the solution won't load without a site on IIS Express existing. Further the contents of the downloaded zip file, while working, the solution does not come with a way to deploy to a new zip so I can create a new zip and deploy. There seem to be files in the zip that are not in the solution so I'm concerned I might not end up with same result just zipping up the files in the solution.
Trying to download the Skeleton but no links to actually download from the app store?
https://virtocommerce.com/skeleton-theme
Starting from the VirtoCommerce.Storefront project.
Copy the contents of the App_Data/Themes/Default folder to a "theme" directory in a new directory.
Create a git repo from the root that contains the "theme" folder.
Add a GitVersion.yml file to control the versioning.
Running in Azure using blob storage you can create a CI process to automatically upload your theme when changes are checked in.
Lastly login to the platform, navigate to the site you uploaded to and activate the new theme. This allows you to fall back if needed.
Zip File
You could also zip the contents of your repo up as well.
The zip file should have a folder in it like "ThemeName-0.0.0", within that folder should be the assets, config, layout, locales, snippets, social and templates folders.
Upload that in the store of your choice and activate.
I'll suggest to use default storefont theme as base theme for customization and educations.
I'm providing some helpful information for helping you to better understand some technical moments related to working with the VC themes:
How theme resources resolving process works:
How to develop custom theme and what technology stack for this use:
Local running pre-compiled platform with installed modules
Local storefront fork (pre-compiled or from source code if you need to future customization)
For case with single theme you might directly change default (global) theme which contains in storefront project App_Data/Themes/default or make separated GitHub repository which will contain only theme and static pages files (as we made for our main site virtocommerce.com theme) and link folder with theme to storefront App_Data/Themes/{store name}/Themes.
Edit theme files in Visual studio code or any other preferred IDE, all changes will be immediately reflected to the local storefront, thanks to the cache invalidation based on theme folder file changes watcher.
Deploy theme changes to staging or productions environment by using any of
convenient CI processes. We are use Jenkins server and Azure Deployment.
Change theme files from manager UI not recommended because you will lose history of changes. And you should use this way only for emergency fixes or for debugging purposes.
So as the title says, I have completed my site for my first client in Dreamweaver ( still studying in college ), Do i just upload it to their hosting site of choice and will all the links work? I know how to upload just curious about how the links like images and my root folder will stay in tact.
Yes, Generally, they will. You can try it for yourself and see. As long as your refering to the images relative to your file.
Upload all your files to your live server's 'htdocs' or 'public-html' folder. All your links should work fine, if done properly. As far as you move all your folders (images, css, etc) to the live server everything will work.
Dreamweaver doesn't require any special thing or configuration before deploying, you can even deploy directly from Dreamweaver to be super sure nothing breaks while deploying to the production server.
Using: Dreamweaver CS6, ColdFusion 10, CFBuilder 3 (soon)
I'm currently developing three seperate web projects but am using the same set of resources for each project:
Same CSS reset and initialisation styles e.g grid layouts
Same JQuery initialisation files
At the moment each web project has a copy of the same files in its web root. I'd like to have a place that all the sites link to get these common shared resources. I can only think of two ways to do this, both similar:
Decide on a 'master' site and place all the CSS and JS files in that site only.
Make a new site called 'shared or common' and put all the common stuff in there. but this new site still has to reside on some domain. So I still need to choose a 'master' project.
Both the above points are somewhat difficult to do because there is no 'master' site. None of the sites are linked in any way to each other.
Say I've decided on a master site then I could then link to those files using a fully qualified URL. But this means that when I am in my development environment I won't be able to see these files and use any kind of IDE introspection to see whats in the files when I make changes (e.g. like intellisense detects whats in the files and gives you hints).
Overall whats the best way to share these resources for both development and production environments?
Update: After the answers I realised I need a virtual directory in IIS and also a virtual folder in my Windows 7 local folders where my web project files are kept.
You need to use web server virtual directories (for IIS) or alias (for Apache).
Simply create an alias/virtual directory called 'scripts' (or whatever you want) in the web root of each site (you can do this in your development environment too, if you are using IIS or Apache) and then simply use
<script src="/scripts/my.js" ></script>
I'll venture an answer.
We have shared assets across HTTP to sister sites and some unrelated sites. But the primary site collapsed and it created a single point of failure that cascaded in insane ways across our other sites (support calls were also insane until we got the primary site fixed).
Nightmare. Never again...
What I suggest is to create an Amazon AWS S3 bucket and host your assets there.
Provided you don't exceed 20,000 requests or 15GB of data per month it is free.
There are lots of setup examples on the internet.
AND if I can set this up and get it working like a charm, then you should have no problem either.
Just a consideration...Good luck.
We do this without sites. Instead we use server mappings. In the CFAdmin tool, we have mapped logical path "/" to a directory path. That directory path has folders for js, images, css, and templates. Then if we want to use a javascript file, it's simply:
<script src = "/js/theFileIWant.js">
I've been working on a website by building it on Joomla. I built it locally with XAMPP and today I copied the files to the directory on the FTP to publish the website and went to the admin panel and there are no plugins or templates, this is weird because I copied the whole folder and imported the database. Already did this twice but it seems to be another error than copy error.
Attention:
I did not install the template and plugins after getting the joomla online, I just copied it to the ftp
Your best bet is to use a tool like Akeeba Backup. This will automate the process and resolve most common issues when moving a Joomla site.