![Maven Central Adds Sigstore Signature Validation](https://cdn.sanity.io/images/cgdhsj6q/production/7da3bc8a946cfb5df15d7fcf49767faedc72b483-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Maven Central Adds Sigstore Signature Validation
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
fesk-home-page
Advanced tools
This project is to create M&S Home Page.
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.
Clone the repository, preferably use ssh (git@github.com:DigitalInnovation/fesk-home-page.git
)
brew update
brew install node
node -v
*Or alternatively you can follow the official NodeJS installation guide.
Only If you are using a MAC.
cd ~/
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.32.1/install.sh | bash
nvm install 10.15.3
For first time installation, within the mns-fe-starter-kit
repository
npm install
The mns-fe-starter-kit
repository is shrink-wrapped (Find more on Shrinkwrapping here - https://docs.npmjs.com/cli/shrinkwrap). Hence the dependencies would be downloaded from npm-shrinkwrap.json instead of from package.json.
To download the latest version of dependencies, delete the npm-shrinkwrap.json file and then
npm install
npm shrinkwrap --dev
(Find more here - https://github.com/DigitalInnovation/fesk-documentation/blob/master/how_tos/shrinkwrap_npm_dependencies.md)
When this is running locally it will run Liniting checks, unit tests and will automatically reload the application when making live code changes both client and server side.
npm run dev
This is how the application is started after deployment to an environment. This requires the bundled assets.
npm start
If you need to create a bundle locally.
npm run bundle
npm run lint:js
to lint all JS files in the src/ directory and webpack config files.npm run lint:sass
to check linting issues in all .scss
and .sass
files in src
directory.A config file named .sass-lint.yml
is added at the root folder which contains the list of files included for lint test and rules. This overrides the default config file which is available with same name in node_module.
npm run test:unit
to run all unit test files that end in .test.js
We have extensive Concourse documentation which can be found here!
Before you can deploy your pipeline you will need to update TEAM_NAME in /ci/deploy-ci-dachs.sh
to your concourse team name.
In majority of the cases deployment should be done via Concourse following the steps listed below:
./deployment/deploy-ci.sh target hash
providing two arguments: target - target enviroments (dev, sit2, sit3, perf or prod), please note: multiple enviroments can be supplied if necessary, hash - hash of the last commit which should be included in the release.Please note: this style of deployment can ONLY be done on master. It is impossible to deploy from a branch using it.
Emergency local deployment is created for the cases where Concourse is unavailable but deployment needs to proceed. To run emergency deploy the following prerequisites must be met.
On Mac:
brew tap cloudfoundry/tap
brew install cf-cli
On Linux:
Use instructions provided in the Cloud Foundry documentation.
chmod a+x path_to_your_downloaded_binary
cf install-plugin path_to_your_downloaded_binary
./deployment/deploy-emergency.sh target hash
where target is the environment you wish to deploy to and hash is the git hash of the commit you wish to deploy
As with deployment from Concourse, this will create a tag on your current branch as a record of deployment.
views
directory.src/server/routes
create a new directory with the handlers and routes you need. Don't forget to load them in src/server/routes/index.js
.src/client
. Add an entry point to the JavaScript file in webpack.config.js
. Require the SCSS file in the javascript file in order for it to be recognised by the build system./src
/client
/examplePage
examplePage.js
examplePage.scss
/server
/routes
/examplePage
handlers.js
handlers.test.js
routes.js
/views
examplePage.hbs
index.js <-- Edit
webpack.config.js <-- Edit
FAQs
Home Page built using FESK
The npm package fesk-home-page receives a total of 1 weekly downloads. As such, fesk-home-page popularity was classified as not popular.
We found that fesk-home-page demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
Research
Security News
Socket researchers uncovered a backdoored typosquat of BoltDB in the Go ecosystem, exploiting Go Module Proxy caching to persist undetected for years.