pablogravielseo

(function() {
	var capturedEvents = [];
	var capturing = false;
	
	function getEventTarget(event) {
		return event.composedPath()[0] || event.target;
	}
		
	function captureEvent(e) {
		if (capturing) {

pablogravielseo

import ApplicationAdapter from 'streetwize-ember/adapters/application';

export default ApplicationAdapter.extend({
  urlForQuery(query) {
    if (query.isSearchQueryFromMapPage) {
      delete query.isSearchQueryFromMapPage
      return `/${this.urlPrefix()}/asset_reports/search`;
    } else {
      return this._super(...arguments);
    }

pablogravielseo

import Service from '@ember/service';
import Bowser from 'bowser';

export default Service.extend({
  getBrowserName() {
    if (window?.navigator?.userAgent) {
      const browser = Bowser.getParser(window.navigator.userAgent);
      if (browser?.parsedResult?.browser?.name) {
        const browserName = browser.parsedResult.browser.name;
        switch(browserName) {

pablogravielseo

$ cd ~/Library/Application\ Support/Postgres/var-10
$ \rm -f postmaster.pid

OR

$ \rm -f ~/Library/Application\ Support/Postgres/var-10/postmaster.pid

pablogravielseo

# Estrutura da pagina

1. header
1.2. navbar
1.2.1. navbar list
1.2.1.1. navbar list item

2. main
2.1. content
2.2. aside 

pablogravielseo

This is the current flow and some details about the implemented features:

1. When the user visits the app, the service worker caches the "index.html" file and the "static assets", 
after that, every page that the user visits it, the service worker caches, 
so for example, if we go to "reports" page, after visiting will cache that page, 
if we go to "surveys" page after visiting will cache and so on. 
If the user disconnect the internet connection (or turn "offline" mode in the browser's dev tools, on network section) and 
refresh the page, the app should still load and the user can navigate between the "cached pages". 

2. We are caching the following resources:

pablogravielseo

Prelude

I. Preface and Motivation

This guide was written because I don't particularly enjoy deploying Phoenix (or Elixir for that matter) applications. It's not easy. Primarily, I don't have a lot of money to spend on a nice, fancy VPS so compiling my Phoenix apps on my VPS often isn't an option. For that, we have Distillery releases. However, that requires me to either have a separate server for staging to use as a build server, or to keep a particular version of Erlang installed on my VPS, neither of which sound like great options to me and they all have the possibilities of version mismatches with ERTS. In addition to all this, theres a whole lot of configuration which needs to be done to setup a Phoenix app for deployment, and it's hard to remember.

For that reason, I wanted to use Docker so that all of my deployments would be automated and reproducable. In addition, Docker would allow me to have reproducable builds for my releases. I could build my releases on any machine that I wanted in a contai

pablogravielseo

Homebrew Permissions Denied Issues Solution

Installing and fixing node.JS

---

brew install node

pablogravielseo

Grab new backup of database

Command: heroku pgbackups:capture --remote production

Response: >>> HEROKU_POSTGRESQL_COLOR_URL (DATABASE_URL) ----backup---> a712

Get url of backup download

Command: heroku pgbackups:url [db_key] --remote production

pablogravielseo

Dir["../image_migrations/establishments/*"].each do |establishment_id_dir|
  Dir["#{establishment_id_dir}/*"].each do |products_dir|
    Dir["#{products_dir}/*"].each do |product|
      extension = File.extname(product).downcase
      name = File.basename(product, extension)
      formatted_name = ActiveSupport::Inflector.transliterate(name).parameterize.downcase.underscore
      path = File.dirname(product)
      new_path = "#{path}/#{formatted_name}#{extension}"

      # puts new_path