“I should really figure out what
that does someday.”
Group items tagged
A Tour of Rails' jQuery UJS - 0 views
-
-
today is that day
-
jquery-ujs wires event handlers to eligible DOM elements to provide enhanced functionality.
- ...11 more annotations...
-
In most cases, the eligible DOM elements are identified by HTML5 data attributes.
-
using JavaScript to progressively enhance the user experience for capable browsers without negatively impacting clients that do not support or do not enable JavaScript.
-
-
jquery-ujs attaches a handler to links with the data-method attribute
-
When the link is clicked, the handler constructs an HTML form along with a hidden input that sets the _method parameter to the requested HTTP verb
-
jquery-ujs attaches a handler to links or forms with the data-confirm attribute that displays a JavaScript confirmation dialog
-
Users double click links and buttons all the time.
-
Links and buttons that have a data-disable-with attribute get a click handler that disables the element and updates the text of the button to that which was provided in the data attribute and disables the button.
-
-
If the action is performed via AJAX, the handler will re-enable the button and reset the text when the request completes.
-
Thanks to jquery-ujs and Rails’ respond_with, setting remote: true is likely the quickest way to get your Rails application making AJAX requests.
-
support both AJAX and standard requests at the same time.
-
Cross-Site Request Forgery (CSRF) is an attack wherein the attacker tricks the user into submitting a request to an application the user is likely already authenticated to.
NetHack 3.6.0: NetHack Home Page - 0 views
-
" Congratulations adventurer! Your quest is at an end for you have reached the home of NetHack. Within, the Wizard of Yendor has no power, the Oracle speaks with utmost clarity, and the grid bugs do not bite. Click friend and enter."
Unique gradient generator - 0 views
-
"This tool helps you to generate beautiful blurry background images that you can use in any project. It doesn't use CSS3 gradients, but a rather unique approach. It takes a stock image, extracts a very small area (sample area) and scales it up to 100%. The browser's image smoothing algorithm takes care of the rest. You can then use the image as an inline, base64 encoded image in any HTML element's background, just click Generate CSS button at the bottom of the app. Select source images from the gallery or use yours, the possibilities are endless."
Using Workflows to Schedule Jobs - CircleCI - 1 views
-
A workflow is a set of rules for defining a collection of jobs and their run order.
-
Schedule workflows for jobs that should only run periodically.
-
run multiple jobs in parallel
- ...37 more annotations...
-
rerun just the failed job
-
Builds without workflows require a build job.
-
Refer the YAML Anchors/Aliases documentation for information about how to alias and reuse syntax to keep your .circleci/config.yml file small.
-
workflow orchestration with two parallel jobs
-
jobs run according to configured requirements, each job waiting to start until the required job finishes successfully
-
requires: key
-
fans-out to run a set of acceptance test jobs in parallel, and finally fans-in to run a common deploy job.
-
Holding a Workflow for a Manual Approval
-
Workflows can be configured to wait for manual approval of a job before continuing to the next job
-
add a job to the jobs list with the key type: approval
-
approval is a special job type that is only available to jobs under the workflow key
-
The name of the job to hold is arbitrary - it could be wait or pause, for example, as long as the job has a type: approval key in it.
-
schedule a workflow to run at a certain time for specific branches.
-
The triggers key is only added under your workflows key
-
using cron syntax to represent Coordinated Universal Time (UTC) for specified branches.
-
By default, a workflow is triggered on every git push
-
the commit workflow has no triggers key and will run on every git push
-
The nightly workflow has a triggers key and will run on the specified schedule
-
Cron step syntax (for example, */1, */20) is not supported.
-
use a context to share environment variables
-
use the same shared environment variables when initiated by a user who is part of the organization.
-
CircleCI does not run workflows for tags unless you explicitly specify tag filters.
-
CircleCI branch and tag filters support the Java variant of regex pattern matching.
-
Each workflow has an associated workspace which can be used to transfer files to downstream jobs as the workflow progresses.
-
The workspace is an additive-only store of data.
-
Jobs can persist data to the workspace
-
Downstream jobs can attach the workspace to their container filesystem.
-
Attaching the workspace downloads and unpacks each layer based on the ordering of the upstream jobs in the workflow graph.
-
Workflows that include jobs running on multiple branches may require data to be shared using workspaces
-
To persist data from a job and make it available to other jobs, configure the job to use the persist_to_workspace key.
-
Files and directories named in the paths: property of persist_to_workspace will be uploaded to the workflow’s temporary workspace relative to the directory specified with the root key.
-
Configure a job to get saved data by configuring the attach_workspace key.
-
persist_to_workspace
-
attach_workspace
-
To rerun only a workflow’s failed jobs, click the Workflows icon in the app and select a workflow to see the status of each job, then click the Rerun button and select Rerun from failed.
-
if you do not see your workflows triggering, a configuration error is preventing the workflow from starting.
-
check your Workflows page of the CircleCI app (not the Job page)
-
"A workflow is a set of rules for defining a collection of jobs and their run order."
Trunk-based Development | Atlassian - 0 views
-
Trunk-based development is a version control management practice where developers merge small, frequent updates to a core “trunk” or main branch.
-
Gitflow and trunk-based development.
-
Gitflow, which was popularized first, is a stricter development model where only certain individuals can approve changes to the main code. This maintains code quality and minimizes the number of bugs.
- ...20 more annotations...
-
Trunk-based development is a more open model since all developers have access to the main code. This enables teams to iterate quickly and implement CI/CD.
-
Developers can create short-lived branches with a few small commits compared to other long-lived feature branching strategies.
-
Gitflow is an alternative Git branching model that uses long-lived feature branches and multiple primary branches.
-
Gitflow also has separate primary branch lines for development, hotfixes, features, and releases.
-
Trunk-based development is far more simplified since it focuses on the main branch as the source of fixes and releases.
-
Trunk-based development eases the friction of code integration.
-
trunk-based development model reduces these conflicts.
-
Adding an automated test suite and code coverage monitoring for this stream of commits enables continuous integration.
-
When new code is merged into the trunk, automated integration and code coverage tests run to validate the code quality.
-
Trunk-based development strives to keep the trunk branch “green”, meaning it's ready to deploy at any commit.
-
With continuous integration, developers perform trunk-based development in conjunction with automated tests that run after each committee to a trunk.
-
If trunk-based development was like music it would be a rapid staccato -- short, succinct notes in rapid succession, with the repository commits being the notes.
-
Instead of creating a feature branch and waiting to build out the complete specification, developers can instead create a trunk commit that introduces the feature flag and pushes new trunk commits that build out the feature specification within the flag.
-
Automated testing is necessary for any modern software project intending to achieve CI/CD.
-
Short running unit and integration tests are executed during development and upon code merge.
-
Automated tests provide a layer of preemptive code review.
-
Once a branch merges, it is best practice to delete it.
-
A repository with a large amount of active branches has some unfortunate side effects
-
Merge branches to the trunk at least once a day
-
The “continuous” in CI/CD implies that updates are constantly flowing.
Getting Started with Rails - Ruby on Rails Guides - 0 views
-
A controller's purpose is to receive specific requests for the application.
-
Routing decides which controller receives which requests
-
The view should just display that information
- ...55 more annotations...
-
view templates are written in a language called ERB (Embedded Ruby) which is converted by the request cycle in Rails before being sent to the user.
-
Each action's purpose is to collect information to provide it to a view.
-
A view's purpose is to display this information in a human readable format.
-
routing file which holds entries in a special DSL (domain-specific language) that tells Rails how to connect incoming requests to controllers and actions.
-
You can create, read, update and destroy items for a resource and these operations are referred to as CRUD operations
-
A controller is simply a class that is defined to inherit from ApplicationController.
-
If not found, then it will attempt to load a template called application/new. It looks for one here because the PostsController inherits from ApplicationController
-
:formats specifies the format of template to be served in response. The default format is :html, and so Rails is looking for an HTML template.
-
:handlers, is telling us what template handlers could be used to render our template.
-
When you call form_for, you pass it an identifying object for this form. In this case, it's the symbol :post. This tells the form_for helper what this form is for.
-
that the action attribute for the form is pointing at /posts/new
-
When a form is submitted, the fields of the form are sent to Rails as parameters.
-
parameters can then be referenced inside the controller actions, typically to perform a particular task
-
params method is the object which represents the parameters (or fields) coming in from the form.
-
Active Record is smart enough to automatically map column names to model attributes,
-
Rails uses rake commands to run migrations, and it's possible to undo a migration after it's been applied to your database
-
every Rails model can be initialized with its respective attributes, which are automatically mapped to the respective database columns.
-
migration creates a method named change which will be called when you run this migration.
-
The action defined in this method is also reversible, which means Rails knows how to reverse the change made by this migration, in case you want to reverse it later
-
Migration filenames include a timestamp to ensure that they're processed in the order that they were created.
-
@post.save returns a boolean indicating whether the model was saved or not.
-
prevents an attacker from setting the model's attributes by manipulating the hash passed to the model.
-
If you want to link to an action in the same controller, you don't need to specify the :controller option, as Rails will use the current controller by default.
-
inherits from ActiveRecord::Base
-
Active Record supplies a great deal of functionality to your Rails models for free, including basic database CRUD (Create, Read, Update, Destroy) operations, data validation, as well as sophisticated search support and the ability to relate multiple models to one another.
-
Rails includes methods to help you validate the data that you send to models
-
Rails can validate a variety of conditions in a model, including the presence or uniqueness of columns, their format, and the existence of associated objects.
-
redirect_to will tell the browser to issue another request.
-
rendering is done within the same request as the form submission
-
Each request for a comment has to keep track of the post to which the comment is attached, thus the initial call to the find method of the Post model to get the post in question.
-
pluralize is a rails helper that takes a number and a string as its arguments. If the number is greater than one, the string will be automatically pluralized.
-
The render method is used so that the @post object is passed back to the new template when it is rendered.
-
The method: :patch option tells Rails that we want this form to be submitted via the PATCH HTTP method which is the HTTP method you're expected to use to update resources according to the REST protocol.
-
it accepts a hash containing the attributes that you want to update.
-
field_with_errors. You can define a css rule to make them standout
-
belongs_to :post, which sets up an Active Record association
-
creates comments as a nested resource within posts
-
call destroy on Active Record objects when you want to delete them from the database.
-
Rails allows you to use the dependent option of an association to achieve this.
-
store all external data as UTF-8
-
you're better off ensuring that all external data is UTF-8
-
use UTF-8 as the internal storage of your database
-
Rails defaults to converting data from your database into UTF-8 at the boundary.
-
:patch
-
By default forms built with the form_for helper are sent via POST
-
The :method and :'data-confirm' options are used as HTML5 attributes so that when the link is clicked, Rails will first show a confirm dialog to the user, and then submit the link with method delete. This is done via the JavaScript file jquery_ujs which is automatically included into your application's layout (app/views/layouts/application.html.erb) when you generated the application.
-
Without this file, the confirmation dialog box wouldn't appear.
-
just defines the partial template we want to render
-
As the render method iterates over the @post.comments collection, it assigns each comment to
-
a local variable named the same as the partial
-
use the authentication system
-
require and permit
-
the method is often made private to make sure it can't be called outside its intended context.
-
standard CRUD actions in each controller in the following order: index, show, new, edit, create, update and destroy.
-
must be placed before any private or protected method in the controller in order to work
Using Infrastructure as Code to Automate VMware Deployments - 1 views
-
Infrastructure as code is at the heart of provisioning for cloud infrastructure marking a significant shift away from monolithic point-and-click management tools.
-
infrastructure as code enables operators to take a programmatic approach to provisioning.
-
provides a single workflow to provision and maintain infrastructure and services from all of your vendors, making it not only easier to switch providers
- ...5 more annotations...
-
A Terraform Provider is responsible for understanding API interactions between and exposing the resources from a given Infrastructure, Platform, or SaaS offering to Terraform.
-
write a Terraform file that describes the Virtual Machine that you want, apply that file with Terraform and create that VM as you described without ever needing to log into the vSphere dashboard.
-
HashiCorp Configuration Language (HCL)
-
the provider credentials are passed in at the top of the script to connect to the vSphere account.
-
modules— a way to encapsulate infrastructure resources into a reusable format.
Auto DevOps | GitLab - 0 views
-
Auto DevOps provides pre-defined CI/CD configuration which allows you to automatically detect, build, test, deploy, and monitor your applications
-
Just push your code and GitLab takes care of everything else.
-
Auto DevOps will be automatically disabled on the first pipeline failure.
- ...78 more annotations...
-
Your project will continue to use an alternative CI/CD configuration file if one is found
-
Auto DevOps works with any Kubernetes cluster;
-
using the Docker or Kubernetes executor, with privileged mode enabled.
-
Base domain (needed for Auto Review Apps and Auto Deploy)
-
Kubernetes (needed for Auto Review Apps, Auto Deploy, and Auto Monitoring)
-
Prometheus (needed for Auto Monitoring)
-
scrape your Kubernetes cluster.
-
project level as a variable: KUBE_INGRESS_BASE_DOMAIN
-
A wildcard DNS A record matching the base domain(s) is required
-
Once set up, all requests will hit the load balancer, which in turn will route them to the Kubernetes pods that run your application(s).
-
review/ (every environment starting with review/)
-
staging
-
production
-
need to define a separate KUBE_INGRESS_BASE_DOMAIN variable for all the above based on the environment.
-
Continuous deployment to production: Enables Auto Deploy with master branch directly deployed to production.
-
Continuous deployment to production using timed incremental rollout
-
Automatic deployment to staging, manual deployment to production
-
Auto Build creates a build of the application using an existing Dockerfile or Heroku buildpacks.
-
If a project’s repository contains a Dockerfile, Auto Build will use docker build to create a Docker image.
-
Each buildpack requires certain files to be in your project’s repository for Auto Build to successfully build your application.
-
Auto Test automatically runs the appropriate tests for your application using Herokuish and Heroku buildpacks by analyzing your project to detect the language and framework.
-
Auto Code Quality uses the Code Quality image to run static analysis and other code checks on the current code.
-
Static Application Security Testing (SAST) uses the SAST Docker image to run static analysis on the current code and checks for potential security issues.
-
Dependency Scanning uses the Dependency Scanning Docker image to run analysis on the project dependencies and checks for potential security issues.
-
License Management uses the License Management Docker image to search the project dependencies for their license.
-
Vulnerability Static Analysis for containers uses Clair to run static analysis on a Docker image and checks for potential security issues.
-
Review Apps are temporary application environments based on the branch’s code so developers, designers, QA, product managers, and other reviewers can actually see and interact with code changes as part of the review process. Auto Review Apps create a Review App for each branch. Auto Review Apps will deploy your app to your Kubernetes cluster only. When no cluster is available, no deployment will occur.
-
The Review App will have a unique URL based on the project ID, the branch or tag name, and a unique number, combined with the Auto DevOps base domain.
-
Review apps are deployed using the auto-deploy-app chart with Helm, which can be customized.
-
Your apps should not be manipulated outside of Helm (using Kubernetes directly).
-
Dynamic Application Security Testing (DAST) uses the popular open source tool OWASP ZAProxy to perform an analysis on the current code and checks for potential security issues.
-
Auto Browser Performance Testing utilizes the Sitespeed.io container to measure the performance of a web page.
-
add the paths to a file named .gitlab-urls.txt in the root directory, one per line.
-
After a branch or merge request is merged into the project’s default branch (usually master), Auto Deploy deploys the application to a production environment in the Kubernetes cluster, with a namespace based on the project name and unique project ID
-
Auto Deploy doesn’t include deployments to staging or canary by default, but the Auto DevOps template contains job definitions for these tasks if you want to enable them.
-
Apps are deployed using the auto-deploy-app chart with Helm.
-
For internal and private projects a GitLab Deploy Token will be automatically created, when Auto DevOps is enabled and the Auto DevOps settings are saved.
-
If the GitLab Deploy Token cannot be found, CI_REGISTRY_PASSWORD is used. Note that CI_REGISTRY_PASSWORD is only valid during deployment.
-
If present, DB_INITIALIZE will be run as a shell command within an application pod as a helm post-install hook.
-
a post-install hook means that if any deploy succeeds, DB_INITIALIZE will not be processed thereafter.
-
DB_MIGRATE will be run as a shell command within an application pod as a helm pre-upgrade hook.
-
-
-
-
-
Once your application is deployed, Auto Monitoring makes it possible to monitor your application’s server and response metrics right out of the box.
-
annotate the NGINX Ingress deployment to be scraped by Prometheus using prometheus.io/scrape: "true" and prometheus.io/port: "10254"
-
If you are also using Auto Review Apps and Auto Deploy and choose to provide your own Dockerfile, make sure you expose your application to port 5000 as this is the port assumed by the default Helm chart.
-
While Auto DevOps provides great defaults to get you started, you can customize almost everything to fit your needs; from custom buildpacks, to Dockerfiles, Helm charts, or even copying the complete CI/CD configuration into your project to enable staging and canary deployments, and more.
-
If your project has a Dockerfile in the root of the project repo, Auto DevOps will build a Docker image based on the Dockerfile rather than using buildpacks.
-
Auto DevOps uses Helm to deploy your application to Kubernetes.
-
Bundled chart - If your project has a ./chart directory with a Chart.yaml file in it, Auto DevOps will detect the chart and use it instead of the default one.
-
Create a project variable AUTO_DEVOPS_CHART with the URL of a custom chart to use or create two project variables AUTO_DEVOPS_CHART_REPOSITORY with the URL of a custom chart repository and AUTO_DEVOPS_CHART with the path to the chart.
-
make use of the HELM_UPGRADE_EXTRA_ARGS environment variable to override the default values in the values.yaml file in the default Helm chart.
-
specify the use of a custom Helm chart per environment by scoping the environment variable to the desired environment.
-
-
-
Your additions will be merged with the Auto DevOps template using the behaviour described for include
-
copy and paste the contents of the Auto DevOps template into your project and edit this as needed.
-
In order to support applications that require a database, PostgreSQL is provisioned by default.
-
Set up the replica variables using a project variable and scale your application by just redeploying it!
-
You should not scale your application using Kubernetes directly.
-
Some applications need to define secret variables that are accessible by the deployed application.
-
Auto DevOps detects variables where the key starts with K8S_SECRET_ and make these prefixed variables available to the deployed application, as environment variables.
-
Auto DevOps pipelines will take your application secret variables to populate a Kubernetes secret.
-
Environment variables are generally considered immutable in a Kubernetes pod.
-
if you update an application secret without changing any code then manually create a new pipeline, you will find that any running application pods will not have the updated secrets.
-
Variables with multiline values are not currently supported
-
The normal behavior of Auto DevOps is to use Continuous Deployment, pushing automatically to the production environment every time a new pipeline is run on the default branch.
-
If STAGING_ENABLED is defined in your project (e.g., set STAGING_ENABLED to 1 as a CI/CD variable), then the application will be automatically deployed to a staging environment, and a production_manual job will be created for you when you’re ready to manually deploy to production.
-
If CANARY_ENABLED is defined in your project (e.g., set CANARY_ENABLED to 1 as a CI/CD variable) then two manual jobs will be created: canary which will deploy the application to the canary environment production_manual which is to be used by you when you’re ready to manually deploy to production.
-
If INCREMENTAL_ROLLOUT_MODE is set to manual in your project, then instead of the standard production job, 4 different manual jobs will be created: rollout 10% rollout 25% rollout 50% rollout 100%
-
The percentage is based on the REPLICAS variable and defines the number of pods you want to have for your deployment.
-
To start a job, click on the play icon next to the job’s name.
-
Once you get to 100%, you cannot scale down, and you’d have to roll back by redeploying the old version using the rollback button in the environment page.
-
With INCREMENTAL_ROLLOUT_MODE set to manual and with STAGING_ENABLED
-
not all buildpacks support Auto Test yet
-
When a project has been marked as private, GitLab’s Container Registry requires authentication when downloading containers.
-
Authentication credentials will be valid while the pipeline is running, allowing for a successful initial deployment.
-
After the pipeline completes, Kubernetes will no longer be able to access the Container Registry.
-
We strongly advise using GitLab Container Registry with Auto DevOps in order to simplify configuration and prevent any unforeseen issues.