update (#62)

* test

* fix

* fix

* update

* update

* clean

* up

.github/dependabot.yml

@@ -4,15 +4,7 @@ updates:
   directory: "/"
   schedule:
     interval: daily
-    time: "04:00"
-  open-pull-requests-limit: 20
-  ignore:
-  - dependency-name: hexo-theme-minidyne
-    versions:
-    - 3.2.4
-  - dependency-name: hexo
-    versions:
-    - 5.4.0
-  - dependency-name: markdownlint
-    versions:
-    - 0.23.0
+- package-ecosystem: github-actions
+  directory: "/"
+  schedule:
+    interval: daily

package.json

@@ -3,29 +3,29 @@
   "version": "1.0.0",
   "private": true,
   "hexo": {
-    "version": "6.0.0"
+    "version": "6.2.0"
   },
   "dependencies": {
-    "hexo": "6.0.0",
+    "hexo": "6.2.0",
     "hexo-clean-css": "^2.0.0",
     "hexo-generator-feed": "^3.0.0",
     "hexo-generator-index": "^2.0.0",
     "hexo-generator-tag": "^1.0.0",
     "hexo-html-minifier": "^1.0.0",
     "hexo-renderer-ejs": "^2.0.0",
-    "hexo-renderer-markdown-it": "^5.0.0",
-    "hexo-renderer-stylus": "^2.0.1",
+    "hexo-renderer-markdown-it": "^6.0.1",
+    "hexo-renderer-stylus": "^2.1.0",
     "hexo-tag-flickr": "github:tomap/hexo-tag-flickr",
-    "hexo-theme-minidyne": "3.2.7",
-    "hexo-uncss2": "^1.0.2"
+    "hexo-theme-minidyne": "3.2.8",
+    "hexo-uncss2": "^2.1.1"
   },
   "devDependencies": {
-    "glob": "^7.2.0",
-    "hexo-server": "^2.0.0",
-    "markdownlint": "^0.24.0"
+    "glob": "^8.0.3",
+    "hexo-server": "^3.0.0",
+    "markdownlint": "^0.26.0"
   },
   "engines": {
-    "node": ">= 12"
+    "node": ">= 16"
   },
   "scripts": {
     "build": "hexo g",

source/_posts/AppVeyor-Setup.md

@@ -28,9 +28,9 @@ The solution was to enable a "Beta FTP" option, ... of course.
 
 Well, at first, I wanted to use SFTP (you know, for security, ...), which is supposed to be enabled on my OVH account, but it did not work. So that's for another day.
 
-To test the deployment, I set the FTP folder to __/www/test/__. Strangely, AppVeyor decided that the best folder to deploy my files was: __/www/test/**public**/..._ instead of directly __/www/test/...__ it was one folder too deep.
+To test the deployment, I set the FTP folder to **/www/test/**. Strangely, AppVeyor decided that the best folder to deploy my files was: **/www/test/\*\*public\*\*/...** instead of directly **/www/test/...** it was one folder too deep.
 
-I googled again and found [that AppVeyor documentation page that helped me](https://www.appveyor.com/docs/packaging-artifacts/#pushing-artifacts-from-scripts). So my solution was to remove the artifact and instead use a PowerShell to publish the files so that their path was __index.html__ instead of __public/index.html__.
+I googled again and found [that AppVeyor documentation page that helped me](https://www.appveyor.com/docs/packaging-artifacts/#pushing-artifacts-from-scripts). So my solution was to remove the artifact and instead use a PowerShell to publish the files so that their path was **index.html** instead of **public/index.html**.
 
 After some trial and errors (~40 of them), I end up with something working. This is all nice and great, but I don't like having all the configuration in AppVeyor, I prefer to have it in my Git Repository, so I can reproduce it somewhere else and I can share it also :)
 

source/resume/index.md

@@ -10,12 +10,13 @@ layout: page
 
 French ecommerce company, pioneer in online flash sales of designer brands.
 
-#### Lead Developer | Mid 2019 to present
+#### Lead Developer | Mid 2019 to May 2022
 
 - Tech Lead on a Public Web Portal
   - Similar to the previous product, but with a React UI
   - Multilingual team, spread across France and Spain
-  - .Net 5, RabbitMQ, PostgreSQL, EntityFramework, NodeJs, React, Express, Helm, ...
+  - Interesting challenges around micro frontends & authentication
+  - .Net 6, RabbitMQ, PostgreSQL, EntityFramework, Yarp, NodeJs, React, Express, Helm, ...
 
 #### Senior Software Developer | Feb 2018 to mid 2019