gdu is a very useful disk usage analyzer in console, except directly install, under Rocky Linux 9, below installation method feels more native:
|
gdu is a very useful disk usage analyzer in console, except directly install, under Rocky Linux 9, below installation method feels more native:
|
Another brand new Ubuntu 22.04 server and another installation log.
|
|
Using nodesource distribution
|
|
|
|
|
|
|
|
|
|
|
|
The puma file which will lauch puma via system service.
|
Like the before 2022 / 2023 year, here is my current subscription, the first number is RMB per month.
So totally 480 RMB per month have to pay, in previous year is 419 RMB, so 14% higher compare with year 2023.
其实这本书可以吐槽的地方非常多,看了几页后,我就有了两个槽点:为啥书名是《华为管理变革》,而不是《华为变革》呢?看书的目录,国际化,研发,供应链,财经,组织,人力各个方面都说到了,为啥要单单强调管理变革呢?还有全书真正和华为密切相关的内容实在不多,绝大多数的内容,将华为改成小米也一样成立,那么这本书的独特性在哪里呢?抱着这两个疑问,又因为这本是直属领导要求的读书会交流书目,我开始了精读。
年轻的时候,觉得一本书最重要的是内容,常常跳过序,现在年纪大了,觉得序和作者是最重要的,序代表的写作的出发点,作者的背景决定了书的方向和内容,《华为管理变革》的第一作者是吴晓波,第二作者是Johann Peter Murmann,成书于 2017 年,是一个国际化合作和充满希望的年代。
本书有两个序,序 2 更值得一读,提到了中澳合作,最优秀的中国企业融入全球化,还有根本的原因,恐惧。序 2 也回答了本文一开始的疑问,因为是管理学院的人书写的,所以必须加上管理两个字。
概述的作者是老外,所以更精读一下,也不知道这 36 页到底给了老外多少钱,华为以客户为第一,通用电器为股东利益为第一次,西南航空以员工满意为第一优先目标,从 2024 年的角度看,这三者显然都不太成功。文中还提到了华为基本法,但是华为基本法从 1998 年后就没有发布过更新版本。任也从曾经的削足适履学习 IBM 到不再遵循基本法,可见华为管理变革的目标就是变革,华为本身是没有目标的,如果活下去不能算作目标的话。
这一章最大的看点还是2007年到2005年任的地位的空前提高,这显然离不开 IPD,让我想起了任的学习毛泽东思想的标兵身份,可见一个组织内的权利收拢必须有外部威胁,也需要内部流程变革,如果是收拢权利的话,这个案例真的值得学习,可惜只能从字里行间读,实在是不直白。
华为主要分三个阶段:
时间关系,就看了两章,总的结论就是华为是一个挺典型的国内企业案例,啥都想做,也没啥目标,后面的国际化全球化其实还是卖货,估计西班牙用了华为很多产品,所以必须建立一个研究中心,总之这些套路也是微软玩下来的,大家都差不多。
一句话总结全文就是,既要还要也要,唯一不变的就是变化,能赚到钱就能请管理学院的人写书,实打实的表示羡慕。
Although dify recommends using Docker, I found that Docker consumes hundreds of gigabytes of storage and makes it difficult to tweak the code on the fly. That's why I decided to install dify.ai from source code.
|
|
|
Or see official document.
Follow the official guide
|
|
|
|
|
following guide
|
reason to choose passenger instead of dify original gunicorn is much user friendly to change something.
|
This configuration sets up HTTP to redirect to HTTPS and configures Passenger for a WSGI application.
|
|
|
|
|
|
|
|
|
|
|
Replace cmd/commandline/version.go and main.go:43 with version
|
|
|
Only after change python part.
|
|
|
|
I'm using an brand new Rocky Linux 9 server, to deploy the pgac_demo project.
|
If htop not found
|
|
|
|
|
|
|
The puma file which will lauch puma via system service.
|
The systemd service file.
|
The nginx conf files.
|
Large following the AnyCable deployment document
|
The anycable-go can download from release page
|
You may need to fix access control for user pgac for letsencrypt key files.
|
|
Rails' default package manager for JS is yarn, and I like yarn because the package installation process on the China network is much more stable, and Capistrano's support for yarn is also great.
However, Angular projects usually use npm as the default project manager. I used to believe it's not changeable because every time I tried to switch, I failed. But yesterday, I found the correct way to do it, and here is how.
Make sure the Angular project works normally in npm.
|
This can be done via the import feature
|
This is required to ensure Angular works after the yarn import. syncyarnlock is a tool that syncs yarn.lock versions into an existing package.json file.
|
After running yarn update, compare the yarn.lock file, add missing dependencies and devDependencies after the yarn update. I guess this is the key step to migrate from npm to yarn because npm dependencies are nested but yarn's are flat.
|
|
You can keep package-lock.json or delete it, but your Angular project works with yarn now!
|
Using nodesource distribution
|
|
Rocky Linux 9 including golang 1.20.
|
Largely following official guide
|
|
|
|
Don't forget change back to more strict setting.
|
|
|
|
|
And open your server like http://172.16.1.47:3000 to configure
Should following document, but if found cmd/web.go:353:listen() [E] Failed to start server: listen tcp 0.0.0.0:443: bind: permission denied error try below:
|
|
|
|
I'm using the same server as post mention, to deploy the pgac_demo project.
|
|
|
|
The puma file which will lauch puma via system service.
|
The systemd service file.
|
The nginx conf files.
|
Large following the AnyCable deployment document
|
The anycable-go can download from release page
|
|
|