Pierre Verkest petrus-v

## monitoring-odoo-postgresql-lock.sh
#!/bin/bash
##################################################################################
##                                                                              ##
## To run this script by command line in background issue this command          ##
##   ./monitoring-odoo-postgresql-lock > /dev/null 2>&1 &                       ##
## To kill this script if running issue this command                            ##
##   pkill -f monitoring-odoo-postgresql-lock                                   ##
## To add this script to crontab:                                               ##
##   @reboot /path/to/monitoring-odoo-postgresql-lock > /dev/null 2>&1 || true  ##
##                                                                              ##

## 0-github-actions.md

      
              2 files
            
          
              85 forks
            
          
              60 comments
            
          
              600 stars
            
          
                domenic
                / 0-github-actions.md
            
            
              Last active
              April 8, 2024 23:35
            
              
                Auto-deploying built products to gh-pages with Travis
              
          
    Auto-deploying built products to gh-pages with GitHub Actions

This is a set up for projects which want to check in only their source files, but have their gh-pages branch automatically updated with some compiled output every time they push.
A file below this one contains the steps for doing this with Travis CI. However, these days I recommend GitHub Actions, for the following reasons:

It is much easier and requires less steps, because you are already authenticated with GitHub, so you don't need to share secret keys across services like you do when coordinate Travis CI and GitHub.
It is free, with no quotas.
Anecdotally, builds are much faster with GitHub Actions than with Travis CI, especially in terms of time spent waiting for a builder.


## console.html
<html>
<head>
    <script type="text/javascript">
        console.log('TEST TEST');
        window.dump('DUMP DUMP');
        console.error('ERROR ERROR');
    </script>
</head>
<body>

## qunit_tests.py
import unittest
from sys import *
import os

from selenium import webdriver
from selenium.webdriver.support.ui import WebDriverWait
from selenium.common.exceptions import NoSuchElementException, TimeoutException

class QUnitTests(unittest.TestCase):
    driver = None
	#!/bin/bash
	##################################################################################
	## ##
	## To run this script by command line in background issue this command ##
	## ./monitoring-odoo-postgresql-lock > /dev/null 2>&1 & ##
	## To kill this script if running issue this command ##
	## pkill -f monitoring-odoo-postgresql-lock ##
	## To add this script to crontab: ##
	## @reboot /path/to/monitoring-odoo-postgresql-lock > /dev/null 2>&1 \|\| true ##
	## ##
	<html>
	<head>
	<script type="text/javascript">
	console.log('TEST TEST');
	window.dump('DUMP DUMP');
	console.error('ERROR ERROR');
	</script>
	</head>
	<body>
	import unittest
	from sys import *
	import os

	from selenium import webdriver
	from selenium.webdriver.support.ui import WebDriverWait
	from selenium.common.exceptions import NoSuchElementException, TimeoutException

	class QUnitTests(unittest.TestCase):
	driver = None