Running your ASP.NET Core (or other) application in Docker using SSL should not be an overwhelming task. These steps should do the trick.
Run the following steps from a Linux terminal (I used WSL or WSL2 on Windows from the Windows Terminal).
It should look something like the content below; call it my-site.conf or something like that.
| Angular CLI version | Angular version | Node.js version | TypeScript version | RxJS version | |
|---|---|---|---|---|---|
| ~16.0.0 | ~16.0.0 | ^16.13.0 || ^18.10.0 | >=4.9.5 <5.1.0 | ^6.5.5 || ^7.4.0 | |
| ~15.2.0 | ~15.2.0 | ^14.20.0 || ^16.13.0 || ^18.10.0 | >=4.8.4 <5.0.0 | ^6.5.5 || ^7.4.0 | |
| ~15.1.0 | ~15.1.0 | ^14.20.0 || ^16.13.0 || ^18.10.0 | >=4.8.4 <5.0.0 | ^6.5.5 || ^7.4.0 | |
| ~15.0.5 | ~15.0.4 | ^14.20.0 || ^16.13.0 || ^18.10.0 | ~4.8.4 | ^6.5.5 || ^7.4.0 | |
| ~14.3.0 | ~14.3.0 | ^14.15.0 || ^16.10.0 | >=4.6.4 <4.9.0 | ^6.5.5 || ^7.4.0 | |
| ~14.2.0 | ~14.2.0 | ^14.15.0 || ^16.10.0 | >=4.6.4 <4.9.0 | ^6.5.5 || ^7.4.0 | |
| ~14.1.3 | ~14.1.3 | ^14.15.0 || ^16.10.0 | >=4.6.4 <4.8.0 | ^6.5.5 || ^7.4.0 | |
| ~14.0.7 | ~14.0.7 | ^14.15.0 || ^16.10.0 | >=4.6.4 <4.8.0 | ^6.5.5 || ^7.4.0 | |
| ~13.3.0 | ~13.3.0 | ^12.20.2 || ^14.15.0 || ^16.10.0 | >=4.4.4 <4.7.0 | ^6.5.5 || ^7.4.0 |
A non-exhaustive list of WebGL and WebGPU frameworks and libraries. It is mostly for learning purposes as some of the libraries listed are wip/outdated/not maintained anymore.
| Name | Stars | Last Commit | Description |
|---|---|---|---|
| three.js | 
Hello, visitors! If you want an updated version of this styleguide in repo form with tons of real-life examples… check out Trellisheets! https://github.com/trello/trellisheets
“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”
You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?
| If you are running a large website where you will need to test new features on a seperate url before pushing them live then the following instructions are for you ;) | |
| For this example imagine your url is apple.com and you want a development/staging site on a subdomain which is dev.apple.com | |
| #Setup# | |
| 1. First thing you'll want to do is go ahead and create your website in plesk and add the subdomain dev.apple.com at the same time. | |
| 2. ssh into the server e.g. $ ssh username@ipaddress | |
| 3. Once logged in cd into the private directory (this will be where all git repos are stored) e.g. $ cd ~/private | |
| 4. Create the main repo e.g. $ git init --bare apple.git | |
| 5. Now to clone this new repo on your local machine. $ git clone ssh://username@ipaddres/~/private/apple.com |
| /* | |
| * Append this to the end of your application/config.php | |
| * @see http://stackoverflow.com/questions/3700626/namespace-in-php-codeigniter-framework#21858556 | |
| */ | |
| spl_autoload_extensions('.php'); // Only Autoload PHP Files | |
| spl_autoload_register(function($classname) { | |
| if (strpos($classname, '\\') !== false) { |
mix3d asked for some help using this guide with windows so here we go. This was tested with Windows 10. Run all commands in Git Bash once it's installed.
Github will be the main account and bitbucket the secondary.
| # Configure the reverse-proxy on port 443 | |
| server { | |
| # general configs | |
| keepalive_timeout 30; | |
| listen 127.0.0.1:443 ssl; | |
| server_name api.example.com; | |
| # ssl configs | |
| ssl_certificate /path/to/api.crt; | |
| ssl_certificate_key /path/to/api.key; |
| App = new Marionette.Application(); | |
| App.addRegions { | |
| "headerRegion": "#header" | |
| "topMenuRegion": "#top-menu" | |
| "mainRegion" : "#main" | |
| } | |
| App.on 'initialize:after', -> | |
| Backbone.history.start() |
I have always struggled with getting all the various share buttons from Facebook, Twitter, Google Plus, Pinterest, etc to align correctly and to not look like a tacky explosion of buttons. Seeing a number of sites rolling their own share buttons with counts, for example The Next Web I decided to look into the various APIs on how to simply return the share count.
If you want to roll up all of these into a single jQuery plugin check out Sharrre
Many of these API calls and methods are undocumented, so anticipate that they will change in the future. Also, if you are planning on rolling these out across a site I would recommend creating a simple endpoint that periodically caches results from all of the APIs so that you are not overloading the services will requests.