Tuesday, 20 October 2026
What Can You Build with Hermes Agent? 5 Production-Grade Workflows
Wednesday, 27 August 2025
Why PM2 Is Not Launching Your Node.js App—and How to Fix It
Broken Your Node.js PM2 — and How to Fix It
Have you ever faced the frustration of manually running your Node.js app only for it to work perfectly—and yet, when launching it via PM2, it stubbornly refuses to respond? This is a surprisingly common issue, but fortunately, one that can often be resolved with a systematic approach.
In modern production environments, PM2 is a trusted manager for running Node.js processes reliably. But when things go wrong, it can feel like a black box—your app shows as “online” yet fails to respond. This blog will walk you through the most frequent culprits, structured troubleshooting steps, and production-level hardening tips to ensure your app stays up and running smoothly.
Common Reasons PM2 Fails to Launch Your Node Process
- Script Path or Filename Errors: A misconfigured script path may lead to silent failures. Verify file references like
server/index.js. - Application Not Listening on the Expected Port: Ensure your app is binding and listening on the correct port.
- Daemon Mode & Execution Context (Especially on Windows): GUI apps may not launch correctly without the
--no-daemonflag. - Missing System Startup Configuration: Without running
pm2 startupand enabling systemd, apps won’t auto-start on reboot. - Node Version Mismatch: After Node upgrades (e.g., via NVM), reinstall and update PM2 to maintain compatibility.
- Cluster Mode Port Conflicts: Avoid
EADDRINUSEerrors by assigning unique ports or using fork mode.
Step-by-Step Troubleshooting Guide
-
Verify Script Path & Logging
Usepm2 logsandpm2 show <app>to inspect the app’s status and confirm the script path. -
Confirm App is Listening on the Correct Port
Usenetstat,lsof, orcurlto ensure the app binds to the expected port. -
Use --no-daemon if Needed
Launch withpm2 start app.js --no-daemonon systems that require GUI compatibility. -
Configure System Startup Properly
Run:pm2 startup # Follow systemd instructions pm2 save -
Reinstall PM2 After Node Updates
After switching Node versions, reinstall PM2 and runpm2 update. -
Avoid Port Conflicts in Cluster Mode
Assign unique ports or switch to fork mode to prevent errors.
Best Practices for Production Stability
- Use
ecosystem.config.jsto define mode, port, memory limits, and restart policies. - Implement logging and health checks using
--watch,--max-memory-restart, and structured formats. - Integrate monitoring tools like ELK, Better Stack, or CloudWatch.
- Ensure proper handling of unhandled promise rejections to avoid silent crashes.
FAQs
- Why does PM2 say my app is “online,” but it’s not responsive?
Likely due to incorrect port binding or silent failure in the startup routine. - How do I make PM2 launch my app after reboot?
Usepm2 startupfollowed bypm2 saveto persist processes. - Why won’t my GUI Node app start with PM2?
Try--no-daemonor start via npm scripts. - What should I do after upgrading Node?
Reinstall PM2 and runpm2 updateto sync versions.
Conclusion
When PM2 isn’t launching your Node.js app, the root cause is usually in environment or configuration. Use this guide to diagnose script path errors, port issues, version mismatches, and system startup configs. With proper setup, PM2 becomes an indispensable tool for Node.js app stability.
Friday, 7 February 2025
Resolving SFTP Import Failures on Amazon AWS: Best Practices for Cloud Development and SRE Engineering
In the fast‐paced world of Cloud Development and SRE Engineering, encountering transient errors can disrupt your workflow. Recently, our team noticed an error during an SFTP import job that failed at 2020-02-20.
The error log indicated an AccessDenied issue when the Lambda function attempted to perform an s3:ListBucket operation on an S3 bucket (e.g. arn:aws:s3:::example-bucket). In this article, we will explore how to diagnose and resolve this issue using Amazon AWS–native techniques, offering insights and practical examples for engineers working in cloud environments.
Understanding the Issue
The Error Scenario
During an SFTP import job, our logs reported the following error:
AccessDenied: User: arn:aws:sts::111111xxxxxx:assumed-role/AxLambdaRole-user-envname/EventBusListenerFunction-envname-user is not authorized to perform: s3:ListBucket on resource: "arn:aws:s3:::example-bucket" because no identity-based policy allows the s3:ListBucket action
Status Code: 403
Request ID: RTDG456GRHUUO1
Our investigation revealed that the job was triggered twice:
- First Invocation (Failure): The job started when the SFTP stream began writing to the S3 bucket. At this point, the file was incomplete, and the Lambda function did not have permission to list the bucket.
- Second Invocation (Success): When the file upload finished, a subsequent trigger led to a successful run.
Team Discussion and Client Feedback
Our internal discussion concluded that the SFTP file was being streamed into the bucket. One of our SRE engineers proposed that the initial trigger occurred when the file stream began, and the second one when the stream completed. However, this double-triggering results in false-positive alerts, as the email notifications indicate.
The client explained:
"Cynthetic Client writes files directly to the SFTP server without first creating a local copy. Changing this behavior would require additional infrastructure and significant time to propose and approve an architectural change in the Data Platform."
They are exploring alternatives, but in the meantime, we need a solution that minimizes false alerts using existing Amazon AWS features.
Amazon AWS–Native Strategies to Resolve the Issue
Here are several strategies that leverage AWS-native services and configurations to address the issue without needing major infrastructure changes.
1. Refine S3 Event Notification Triggers
Use Specific Event Types:
- Instead of triggering on every object creation event, configure your S3 bucket to send notifications only when the file upload is complete.
- If your process uses multipart uploads, configure the event to trigger on the
s3:ObjectCreated:CompleteMultipartUploadevent. - Refer to the Amazon S3 Event Notifications documentation for more details.
Apply Object Key Filters:
- Encourage your partners to add a specific suffix (e.g.,
.complete) to file names when the file is fully uploaded. - Update the event configuration to trigger only on objects that match this pattern.
2. Utilize SQS with Delayed Processing
Route Events Through an SQS Queue:
- Instead of triggering the Lambda function directly from the S3 event, configure the bucket to send events to an Amazon SQS queue.
- This allows you to introduce a delay or buffer time before processing the event.
Implement Delay or Validation in Lambda:
- Within your Lambda function, add logic to check whether the file upload is complete by verifying object metadata (e.g., size or custom tags).
- If the file is incomplete, the function can ignore the event or re-queue it for later processing.
- Learn more about integrating SQS with Lambda in the AWS Lambda Developer Guide.
3. Adjust the IAM Policy for the Lambda Role (Temporary Workaround)
Grant s3:ListBucket Permission:
- As a short-term measure, update the IAM policy attached to the Lambda’s role to allow
s3:ListBucketon the S3 bucket. - This can prevent the Lambda function from failing the initial check.
- However, note that even with the permission granted, if the file is incomplete, your processing logic may still encounter issues.
- For more on IAM policies, refer to the AWS IAM User Guide.
4. Work with Your SFTP Partner
Discuss Alternative Upload Approaches:
- Engage with your SFTP provider (in our case, Synthetic Client) and ask if they could temporarily stream the file to a staging area or use a naming convention to indicate when the file is fully uploaded.
- Although the client mentioned that changing this process requires additional infrastructure and lengthy approvals, a dialogue might uncover interim solutions.
Example: Implementing an SQS-Delayed Lambda Trigger
Below is an example configuration for routing S3 events through SQS with a delay, minimizing false alerts.
Configure S3 to Send Notifications to SQS:
- In your S3 bucket settings, set up an event notification that sends events for the CompleteMultipartUpload to an SQS queue.
- Learn how to configure S3 event notifications.
Set a Delay on the SQS Queue:
- When creating the SQS queue, set a delivery delay (e.g., 60 seconds) to allow the file stream to complete.
- SQS Delay Queue Documentation.
Update Your Lambda Function:
- Modify the Lambda code to check if the object exists in its complete form. For example, use the
HeadObjectAPI to verify file size or metadata. - Process the event only if the file meets the completeness criteria.
- Modify the Lambda code to check if the object exists in its complete form. For example, use the
Conclusion
By refining your S3 event triggers, leveraging Amazon AWS services like SQS for delayed processing, and, if necessary, temporarily adjusting IAM policies, you can reduce false alarms caused by premature Lambda invocations during SFTP streaming uploads. This approach aligns with best practices in Cloud Development and SRE Engineering, ensuring your systems remain robust and secure without incurring significant additional costs.
For further reading, check out these official resources:
Implementing these solutions can help your team manage SFTP imports more reliably while reducing unwanted alerts. This method exemplifies how strategic configuration in Amazon AWS can streamline Cloud Development processes and enhance the operational efficiency expected in modern SRE Engineering practices.
Happy cloud developing!
Tuesday, 3 September 2024
How do I build automation with ChatGPT and keep my system running with Ansible
Simplify Your Ansible Playbook Creation with ChatGPT
Are you tired of writing complex Ansible playbooks manually? Want to streamline your DevOps processes and save time? Look no further! I’ve just released a new video that shows you how to use ChatGPT to simplify and speed up the process of generating Ansible code.
In the video, I walk you through several practical examples where ChatGPT helps in automating the creation of Ansible playbooks. Whether you’re checking system resources, verifying Java installations, monitoring WebSphere applications, or ensuring your filesystems aren’t running out of space, ChatGPT can help you generate the required playbook code with ease.
What You’ll Learn:
System Resource Monitoring:
- Learn how to create an Ansible playbook that monitors CPU, memory, disk, and network usage across your servers.
Conditional Logic for Different Linux Distros:
- See how to write playbooks that adapt to different Linux distributions, ensuring that the correct commands are executed regardless of the environment.
Java and WebSphere Application Checks:
- Discover how to automate the process of checking for Java installations and monitoring the status of WebSphere Application Server instances.
Filesystem Usage Alerts:
- Watch how to create a playbook that checks filesystem usage and triggers alerts if any directory exceeds a specified storage threshold.
Why This Video is Essential:
Ansible is a powerful tool for automating IT infrastructure, but writing playbooks can be time-consuming and error-prone. By leveraging ChatGPT, you can generate accurate, optimized code faster and with less effort. This video is a must-watch for DevOps professionals, system administrators, and anyone looking to improve their Ansible workflows.
Watch the video now to see how ChatGPT can transform your approach to Ansible playbook creation and make your automation tasks more efficient than ever!
Monday, 19 August 2024
Ansible is giving below error - consul1 | UNREACHABLE!
Hello all and welcome again into my DevSecOps Blog!!
I am getting the below error while running the ansible consul1 -m ping on my Debian controller and host..
"changed": false,
"msg": "Failed to create temporary directory.In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in \"/tmp\", for more error information use -vvv. Failed command was: ( umask 77 && mkdir -p \"` echo /home/ansible/.ansible/tmp `\"&& mkdir \"` echo /home/ansible/.ansible/tmp/
"unreachable": true
}
The error message you're encountering suggests that Ansible is unable to create a temporary directory on the remote host. This issue is often related to permissions or the remote user not having the necessary privileges to create directories in the specified path.
Here’s a breakdown of the possible causes and steps you can take to troubleshoot and resolve this issue:
1. Permission Issues on the Remote Host
- Issue: The user under which Ansible is executing commands (likely
ansiblebased on the paths) might not have the necessary permissions to create directories in the/home/ansible/.ansible/tmpdirectory. - Solution: Ensure that the remote user has appropriate permissions to write to the
/home/ansible/.ansible/tmpdirectory. You can do this by connecting to the remote host and manually checking the permissions:If thebashssh user@remote_host mkdir -p /home/ansible/.ansible/tmpansibleuser cannot create the directory, adjust the permissions or usesudoas needed.
2. Insufficient Space or Quota Limits
- Issue: The remote system might be out of disk space, or the user might have hit their quota limit, preventing directory creation.
- Solution: Check the available disk space on the remote host with:
Also, check if there are any quota limits set for the user:bashdf -h
Ensure that there is sufficient space, and no quota limits are being exceeded.bashquota -v ansible
3. Invalid or Non-Standard Shell Environment
- Issue: The shell environment might not be set up correctly, or the shell is non-standard, which might cause issues with command execution.
- Solution: Verify the shell environment for the user, and ensure that it’s a standard shell like
bashorsh. You can also check if the shell initialization files (.bashrc,.profile, etc.) are misconfigured or not being executed properly.
4. Change the Remote Temporary Directory Path
- Issue: The default temporary directory might not be accessible or appropriate.
- Solution: Change the temporary directory to a path under
/tmpin youransible.cfg. You can do this by adding or updating the following setting in youransible.cfg:This setting will ensure that the temporary directory is created inini[defaults] remote_tmp = /tmp/.ansible/tmp/tmp, which is generally accessible by all users.
5. Verbose Output for Detailed Error Information
- Issue: The error message might not provide enough details.
- Solution: Run the Ansible command with the
-vvvflag for verbose output to get more detailed information:
This will give you more insight into what’s failing and why.bashansible consul1 -m ping -vvv
By following these steps, you should be able to identify the root cause of the issue. Let me know if any particular step is unclear, or if you encounter any additional errors while troubleshooting!
Tuesday, 16 July 2024
How to Use Jenkinsfile to connect into Ansible Tower and execute a server reboot running a ansible playbook ?
Let’s create a Jenkinsfile that integrates with Ansible Tower and executes a playbook to reboot a server. We’ll also include parameters for environment, target hostname group, and boolean options.
First, make sure you have the following prerequisites:
- Jenkins: Set up Jenkins on your system.
- Ansible Tower: Ensure you have Ansible Tower installed and configured.
- SSH Key Pair: Set up an SSH key pair for authentication between Jenkins and Ansible Tower.
Now, let’s create the Jenkinsfile:
pipeline {
agent any
parameters {
string(name: 'ENV', description: 'Environment (e.g., dev, staging, prod)')
string(name: 'TARGET_HOSTNAME_GROUP', description: 'Ansible inventory group for target hosts')
booleanParam(name: 'REBOOT_ENABLED', defaultValue: true, description: 'Enable server reboot')
}
stages {
stage('Checkout') {
steps {
checkout scm
}
}
stage('Run Ansible Playbook') {
steps {
script {
def ansiblePlaybookCmd = """
ansible-playbook -i ${TARGET_HOSTNAME_GROUP} playbook.yml
--extra-vars 'reboot_enabled=${REBOOT_ENABLED}'
"""
sh ansiblePlaybookCmd
}
}
}
}
}
Explanation:
- The Jenkinsfile defines a pipeline with two stages: “Checkout” and “Run Ansible Playbook.”
- We use parameters to allow users to input the environment, target hostname group, and whether to enable server reboot.
- In the “Run Ansible Playbook” stage, we execute the Ansible playbook using the provided parameters.
- The
ansible-playbookcommand includes the inventory group and an extra variable (reboot_enabled) to control the reboot behavior.
Make sure to adjust the playbook.yml path and customize the playbook according to your specific requirements. Additionally, ensure that Jenkins has the necessary permissions to execute Ansible playbooks on the target hosts.
Remember to replace placeholders (such as ${TARGET_HOSTNAME_GROUP}) with actual values in your environment. If you encounter any issues, feel free to ask for further assistance! 🚀
- For more information on integrating Ansible with Jenkins, you can explore the official Ansible Tower plugin for Jenkins1.
- Additionally, check out the Red Hat blog post on integrating Ansible with Jenkins in a CI/CD process2..
####################################################################
Let’s enhance the Jenkinsfile by adding the three boolean parameters: reboot, stop_application, and start_application. These parameters will allow you to control additional actions during your pipeline execution. Here’s the updated Jenkinsfile:
pipeline {
agent any
parameters {
string(name: 'ENV', description: 'Environment (e.g., dev, staging, prod)')
string(name: 'TARGET_HOSTNAME_GROUP', description: 'Ansible inventory group for target hosts')
booleanParam(name: 'REBOOT_ENABLED', defaultValue: true, description: 'Enable server reboot')
booleanParam(name: 'STOP_APP_ENABLED', defaultValue: false, description: 'Stop application before reboot')
booleanParam(name: 'START_APP_ENABLED', defaultValue: false, description: 'Start application after reboot')
}
stages {
stage('Checkout') {
steps {
checkout scm
}
}
stage('Run Ansible Playbook') {
steps {
script {
def ansiblePlaybookCmd = """
ansible-playbook -i ${TARGET_HOSTNAME_GROUP} playbook.yml
--extra-vars 'reboot_enabled=${REBOOT_ENABLED}'
--extra-vars 'stop_app_enabled=${STOP_APP_ENABLED}'
--extra-vars 'start_app_enabled=${START_APP_ENABLED}'
"""
sh ansiblePlaybookCmd
}
}
}
}
}
Explanation:
- I’ve added three new boolean parameters:
STOP_APP_ENABLEDandSTART_APP_ENABLED. - If
STOP_APP_ENABLEDis set to true, the pipeline will stop the application before rebooting the server. - If
START_APP_ENABLEDis set to true, the pipeline will start the application after the server reboot.
Remember to adjust the playbook (playbook.yml) to handle these additional actions based on the provided parameters. Feel free to customize the playbook according to your specific requirements.
Tuesday, 9 July 2024
How to Write a DevOps Handover Document
A DevOps Handover document template to help a person leaving a project pass on the work done to another engineer, so it is continued, the work is around the Ansible playbook, for ci/cd automation, Jenkins pipeline and GitLab repository..
##### BEGINNING OF DOCUMENT TEMPLATE #########
DevOps Handover Document
Project Overview
Provide a brief overview of the project, its objectives, and its key components.
- Project Name:
- Project Description:
- Key Stakeholders:
- Project Timeline:
- Current Status:
Ansible Playbook
Overview
Provide an overview of the Ansible playbook used in the project.
- Purpose: Describe the purpose of the playbook.
- Main Playbooks and Roles: List the primary playbooks and roles, their locations, and their functions.
- Dependencies: Outline any dependencies or prerequisites for running the playbooks.
Directory Structure
├── ansible/ │ ├── playbooks/ │ │ ├── main_playbook.yml │ │ └── other_playbooks.yml │ ├── roles/ │ │ ├── role1/ │ │ └── role2/ │ ├── inventory/ │ │ ├── production │ │ └── staging │ └── ansible.cfg
- Playbooks: Detailed description of key playbooks and their functions.
- Roles: Detailed description of key roles and their tasks.
- Inventory: Description of the inventory files and their purpose.
- Configuration: Any special configurations in
ansible.cfg.
Running Playbooks
Provide step-by-step instructions for running the playbooks.
- Setup Environment:bash
ansible-playbook -i inventory/production main_playbook.yml - Common Commands:
- Command for running a specific playbook.
- Command for running playbooks in staging/production environments.
- Command for checking the playbook syntax.
- Any other relevant commands.
CI/CD Automation
Jenkins Pipeline
Overview
Provide an overview of the Jenkins pipeline configuration.
- Purpose: Describe the pipeline’s role in the project.
- Pipeline Stages: List and describe each stage of the pipeline.
Configuration
- Jenkinsfile Location:
- Pipeline Script: Provide a snippet or full script of the Jenkinsfile if possible.
- Plugins: List the Jenkins plugins used and their purposes.
Common Tasks
- Triggering Builds: How to manually trigger builds.
- Monitoring Builds: How to monitor build status and logs.
- Debugging Issues: Steps to debug common issues.
GitLab Repository
Overview
Provide an overview of the GitLab repository setup.
- Repository URL:
- Branches: List and describe the purpose of key branches (e.g.,
main,develop,feature/*,hotfix/*). - Branching Strategy: Explain the branching strategy used in the project.
- Merge Requests: Outline the process for creating and reviewing merge requests.
Repository Structure
bash├── .gitlab/
│ ├── ci/
│ │ ├── stages/
│ │ ├── jobs/
│ │ └── scripts/
├── src/
│ ├── main/
│ └── test/
├── docs/
└── README.md
- Key Directories: Description of key directories and their contents.
- CI Configuration: Details of GitLab CI configuration (
.gitlab-ci.yml).
Common Tasks
- Cloning the Repository:bash
git clone <repository_url> - Working with Branches:
- Creating a new branch.
- Merging branches.
- CI/CD Pipelines:
- How to trigger pipelines.
- Monitoring pipeline status.
- Debugging failed pipelines.
Contacts and Resources
Provide a list of key contacts and resources for further assistance.
- Project Manager: Name, email, phone number.
- Technical Lead: Name, email, phone number.
- Relevant Documentation: Links to any additional documentation or resources.
- Access Credentials: Securely provide any necessary credentials or access details.
Additional Notes
Any additional notes, tips, or important information to be aware of.
Prepared by: [Your Name]
Date: [Date]
##### END OF DOCUMENT TEMPLATE #########
Monday, 8 July 2024
Kubernetes CKA Exam preparation Links
Here is a link to of links for the material to help me prepare for the Kubernetes Administration Exam.
- https://go-talks.appspot.com/github.com/jecnua/notes-presentations/notes/containers/orchestration/k8s/certifications/00-preparation.article
- https://go-talks.appspot.com/github.com/jecnua/notes-presentations/notes/containers/orchestration/k8s/certifications/01-cka.article
- https://go-talks.appspot.com/github.com/jecnua/notes-presentations/notes/containers/orchestration/k8s/certifications/02-questions.article
- Kubernetes Docs online docs - https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/
- Kubernetes Change Context -- https://stackoverflow.com/questions/43643463/how-to-switch-kubectl-clusters-between-gcloud-and-minikube
- Kubernetes Cheat Sheet - https://kubernetes.io/docs/reference/kubectl/cheatsheet/
- How to Set Up Ingress On Kubernetes Using Nginx Controller - https://devopscube.com/setup-ingress-kubernetes-nginx-controller/
- Deploy Nginx on K8 - https://www.techrepublic.com/article/how-to-deploy-nginx-on-a-kubernetes-cluster/
- Nginx TLS - K8 - https://boxboat.com/2018/07/02/kubernetes-nginx-ingress-tls-secrets-all-namespaces/
- Manchester Exams Centers - https://www.ielts-exam.net/test-center-search/the-united-kingdom/england/manchester
Saturday, 6 July 2024
The Ultimate List of Python YouTube Channels – Real Python
These are materials which can be used when learning to code in Python
The Ultimate List of Python YouTube Channels
- Al Sweigart
- Anaconda Inc.
- Christian Thompson
- Clever Programmer
- CodingEntrepreneurs
- Corey Schafer
- Chris Hawkes
- CS Dojo
- Data School (Kevin Markham)
- David Beazley
- Enthought
- Michael Kennedy (Talk Python)
- PrettyPrinted
- PyCon Session Recordings
- PyData
- Real Python
- Reuven Lerner
- Sentdex (Harrison Kinsley)
- Socratica
- TheNewBoston (Bucky Roberts)
- Smaller Python Conferences
- Focus on Python tutorials
- Not be brand-new (> 2,000 subscribers)
- Be active (new videos are coming out) OR have an interesting archive with old content worth watching
Al Sweigart
“Tons of sweet computer related tutorials and some other awesome videos too!”
- Website: automatetheboringstuff.com
- Twitter: @AlSweigart
- Subscribe: YouTube
Anaconda Inc.
“With over 4.5 million users, Anaconda is the world’s most popular Python data science platform. Anaconda, Inc. continues to lead open source projects like Anaconda, NumPy and SciPy that form the foundation of modern data science. Anaconda’s flagship product, Anaconda Enterprise, allows organizations to secure, govern, scale and extend Anaconda to deliver actionable insights that drive businesses and industries forward.”
Christian Thompson
“A little bit about me and a lot about Python programming for beginners. I am a middle and high school teacher who uses Python as my teaching language. I firmly believe anyone can (and should) learn to program a computer and that Python is the perfect language for doing so.”
- Website: christianthompson.com
- Twitter: @tokyoedtech
- Subscribe: YouTube
Clever Programmer
“You can find awesome programming lessons here! Also, expect programming tips and tricks that will take your coding skills to the next level.”
CodingEntrepreneurs
“Coding for Entrepreneurs is a Programming Series for Non-Technical Founders. Learn Django, Python, APIs, Accepting Payments, Stripe, jQuery, Twitter Bootstrap, and much more.”
- Website: www.codingforentrepreneurs.com
- Twitter: @joincfe
- Subscribe: YouTube
Corey Schafer
“This channel is focused on creating tutorials and walkthroughs for software developers, programmers, and engineers. We cover topics for all different skill levels, so whether you are a beginner or have many years of experience, this channel will have something for you.”
Chris Hawkes
“We’re going to learn about programming, web design, responsive web design, Reactjs, Django, Python, web scraping, games, forms applications and more!”
CS Dojo
“Hey everyone! My name is YK, and I make videos mostly about programming and computer science here.”
Data School (Kevin Markham)
“You’re trying to launch your career in data science, and I want to help you reach that goal! My in-depth tutorials will help you to master crucial data science topics using open source tools like Python and R.”
David Beazley
“An archive of David Beazley’s conference, user group, and training talks.”
Enthought
“For more than 15 years, Enthought has built AI solutions with science and engineering at the core. We accelerate digital transformation by enabling companies and their people to leverage the benefits of Artificial Intelligence and Machine Learning.”
Michael Kennedy (Talk Python)
“Videos, demos, and lectures about programming - especially Python and web topics.”
PrettyPrinted
“I’m Anthony. I make programming videos.”
- Website: prettyprinted.com
- Twitter: @pretty_printed
- Subscribe: YouTube
PyCon Session Recordings
PyData
“PyData provides a forum for the international community of users and developers of data analysis tools to share ideas and learn from each other. The global PyData network promotes discussion of best practices, new approaches, and emerging technologies for data management, processing, analytics, and visualization. PyData communities approach data science using many languages, including (but not limited to) Python, Julia, and R.”
- Website: pydata.org
- Twitter: @PyData
- Subscribe: YouTube
Real Python
“Python tutorials and training videos for Pythonistas that go beyond the basics. On this channel you’ll get new Python videos and screencasts every week. They’re bite-sized and to the point so you can fit them in with your day and pick up new Python skills on the side.”
Reuven Lerner
“I’m Reuven Lerner, and I teach Python and data science to companies around the world. On this YouTube channel, I publish videos that will help you with Python programming.”
Sentdex (Harrison Kinsley)
“Python Programming tutorials, going further than just the basics. Learn about machine learning, finance, data analysis, robotics, web development, game development and more.”
Socratica
“Socratica makes high-quality educational videos on math and science. New videos every week! We’re a couple of Caltech grads who believe you deserve better videos. You’ll learn more with us!”
TheNewBoston (Bucky Roberts)
“Tons of sweet computer related tutorials and some other awesome videos too!”
Smaller Python Conferences
- EuroPython
- EuroSciPy
- Kiwi PyCon
- PyCascades
- PyCon Argentina (Ar)
- PyCon Australia (AU)
- PyCon Canada
- PyCon Czech (CZ)
- PyCon Finland
- PyCon Germany (DE)
- PyCon Hong Kong (HG)
- PyCon Ireland (IE)
- PyCon Italy (Nove)
- PyCon Japan (JP)
- PyCon Korea (KR)
- PyCon Malaysia (MY)
- PyCon Phillipines (PH)
- PyCon Poland (PL)
- PyCon Singapore (SG)
- PyCon Slovakia (SK)
- PyCon Ukraine (UA)
- PyCon United Kingdom (UK)
- PyGotham 2017
- PyOhio
What Can You Build with Hermes Agent? 5 Production-Grade Workflows
Unlike standard, single-session chat interfaces, Hermes Agent operates as a persistent, self-improving AI runtime. By combining disk st...
-
How To Hide and unhide the hard disk Volumes using CMD Commands : First check how many drives are there in my computer and then s...
-
Based on readers’ feedback, here are some of the best books on Terraform Infrastructure as Code: Continuous Delivery with Jenkins, Kubernet...
-
In the rapidly evolving landscape of software development, the term " DevOps " has gained significant prominence. DevOps, short fo...


