DEV Community: Catherine Anokwuru

How to host your website on Go54 (formerly whogohost)

Catherine Anokwuru — Thu, 04 Apr 2024 16:57:32 +0000

What is Go54

Go54 (formerly Whogohost) is a web hosting platform in Nigeria that leverages shared hosting to cater to a wide range of customers. They offer services such as domain registration, web hosting, website building, email hosting, etc. Go54 leverages cPanel as the control panel for managing their hosting accounts. Through cPanel, customers can perform various tasks related to website management, such as creating email accounts and deploying websites.

How to deploy your website using Go54

To deploy your website using Go54, you need to have purchased both a domain name and a hosting package. There are two primary methods for deploying your website: uploading your folder and using Git version control.

Uploading your folder

When you log in to your Go54 account, you'll be directed to the dashboard. From there, you can access various features and settings related to your hosting account. In the dashboard, you go to files and click on file manager to navigate to your file manager.

Once you’re in your file manager, go into the public_html folder, delete the index.html file there, and proceed to add your file by clicking on upload.

After clicking on upload, you will see the upload box, go ahead and add your files. Please note that you are not permitted to add folders directly. Therefore, you'll need to add your files one by one or select multiple files and drop them into the upload box.
Ensure that your homepage is saved with a filename such as "index.html", "index.php", or any other appropriate format. This is necessary as the web server looks for an "index" file to display as the default homepage of your website.
Once you have uploaded your files, your site is ready to be viewed.

Initializing with a public github repo

When you log in to your account, you will be directed to the dashboard. In the dashboard, you go to files and click on Git version control.

In the Git version control interface, click on "Create" to add your Git repository. You have the option to either clone an existing repository by adding its public repository URL or create a new repository. If creating a new repository, provide your details and click on the "Update" button. Once done, return to the Git version control interface.

When you go back to the Git version control interface, you will notice that your repository has been added. Click on the “Manage” button to checkout to your preferred branch and deploy.

For deployment to be successful, your repository must meet the following requirements:

At least one branch: Your repository must have at least one branch, either locally or remotely. This ensures that there is a source from which changes can be pulled for deployment.
No uncommitted changes: Ensure there are no uncommitted changes in your repository before deploying. Commit any pending changes before deploying.
Valid .cpanel.yml file: Your repository must contain a valid .cpanel.yml file in the top-level directory. This file contains configuration settings that specify how your website should be deployed on the server. If your repository doesn't already have this file, you can add it manually.
- Navigate to the File Manager.
- Go to the repositories section and locate your repository.
- Add a new file named ".cpanel.yml" in the top-level directory.

Edit and add the following to the .cpanel.yml file and save:

---
deployment:
  tasks:
    - export DEPLOYPATH=/home2/username/public_html/
    - /bin/cp index.html $DEPLOYPATH
    - /bin/cp logo.png $DEPLOYPATH
    - /bin/cp icon.jpg $DEPLOYPATH
    - /bin/cp -R assets $DEPLOYPATH

Make sure to replace "username" with your actual username or the appropriate directory path. Also, replace the file and folder names to match your file and folder names, you can add as many as you wish. The files added here are the files that are going to be deployed during deployment.
After you have added the .cpanel.yml file to your repository, navigate back to the Git version control section and select the "Manage" button for your repository. From there, proceed to the "Pull/Deploy" option, and then click on the "Deploy HEAD Commit" button to start the deployment process.

Your site is live and you can easily update your website by pushing changes to the repository.
PLEASE NOTE THAT THIS ONLY WORKS FOR PUBLIC REPOSITORIES. TO INTEGRATE PRIVATE REPOSITORIES, YOU WOULD NEED AN SSH KEY.

CONCLUSION

In conclusion, deploying a website on Go54 can be a seamless process if you follow the necessary steps and adhere to the specified requirements.
If you have any thoughts or experiences to share, please feel free to leave them in the comment section below. Your feedback is valuable and can help improve the deployment experience for others.

Understanding and Navigating Roles in Developer Relations

Catherine Anokwuru — Wed, 17 Jan 2024 11:14:41 +0000

The term "DevRel" has been circulating within the tech ecosystem for some time, and you might have come across it, wondering about its meaning. Although DevRel is a relatively new career path in the tech industry, its roles have been present for a while. Organizations have been engaging in DevRel roles and these responsibilities have only just recently been defined under the umbrella of DevRel.
DevRel simply acts as a go-between for developers and the community, as well as the organization’s products and its customers. It entails having a good understanding of the product and technology, communicating effectively with users, gathering and interpreting their feedback, and transforming them into practical solutions that can be implemented.
DevRel also makes the work of developers easier by actively engaging with the challenges they encounter. It involves learning about these issues, understanding them and crafting effective solutions and best practices to address them.

What are the Roles Associated with DevRel

DevRel is a broad term that encompasses various roles. It includes responsibilities for managing communities, developers, and products. Some roles are interconnected, and individuals may end up handling more than one of these responsibilities in their positions.The roles include, but are not limited to:

Developer Evangelist: A developer evangelist is someone who promotes an organization’s technology or product. They are representatives of the organization’s technology. They work to raise awareness about a company’s product or technology, build support, and influence opinions or decisions in its favor.
Developer Advocate: A developer advocate, as the name implies, is someone who supports and promotes the interests of developers. They interact directly with developers and work to enhance the developer’s skills and productivity by assisting the developers in using tools effectively. The major aim of the developer advocate is to ensure ease for the developer as much as they possibly can and make sure that the product and tools they advocate for provide the best developer experience. They also gather feedback from developers and communicate it to the company, and vice versa. Their tasks include writing technical articles, writing documentation, developing code samples, speaking at events, creating content, contributing to developer forums, and so on
Developer Experience Engineer: DevEx Engineer can be used interchangeably with Developer advocate, due to their overlapping responsibilities. The DevRel engineer has a strong technical background and holds a technical position within a company. They work in close collaboration with the product and engineering teams to understand the technology and products the company builds.
Community Manager: A community manager is responsible for overseeing the operations of the developer community associated with a product, or technology. They handle the community and keep communication open, thereby bridging the gap between the community and developers. They organize events, handle community socials, collect community feedback, organize meetups and conferences, and so on. To the community, the community manager is the representative of the company and to the company, the community manager is the representative of the community.

Should DevRel be adopted in all organizations?

What DevRel means differs from one organization to another. Its definition and job description tend to vary based on the organization and its specific needs. So while a company might have a DevRel department to deal with issues faced by developers who use their product, another might have a DevRel team to provide developers with the best tools and products to enhance productivity. Some organizations utilize DevRel to create awareness regarding a product and market it to developers, while others employ it to manage their growing community of developers. What developer relations mean to an organization depends on what the company’s goals and objectives are.

It is essential to recognize that DevRel centers around developers as the primary audience. Be it marketing to developers, providing developers with tools to make their work easier, or creating educational content, the core focus remains on developers. While DevRel advocates might work with the product or marketing team from time to time, all of these efforts are still geared towards developers.

Not all organizations need a DevRel department. Companies that have people working in DevRel are companies with products targeted at developers or products that have to do with the development process. So if you need someone to market and promote your product, but your product has nothing to do with developers, you might just need a sales/marketing team. If you need someone to create content and write about your product but your product has nothing to do with developers, a content creator might be more appropriate. If you need someone to collect feedback about your product but your product has nothing to do with developers, a customer support officer may be more fitting.

Some companies are more interested in the developer's productivity and how best their products work for the developers, while some are more interested in marketing their products. Others are more interested in getting feedback from the community. Whatever the goal of the company may be, the question to ask is ‘Who are my customers?’, if your answer isn’t developers and your product has nothing to do with the development process, then you probably don’t need a DevRel department.

Skills Needed in DevRel

Technical skills
To work in DevRel, you need to have some technical skills. The depth of the technical skills needed varies from role to role. For example, DevEx Engineers usually need to have a strong technical background in their fields to be able to perform their roles well, but a community manager does not need as much technical knowledge to be able to perform well in the role. It is advisable to have at least a basic understanding of developer tools, especially the ones used in your company, as you will be relating to developers most of the time, and to relate well with them and build trust you need to speak their language.

Taking initiative and being proactive
Measuring success in DevRel is difficult as it is not quantifiable. Because of this, you need to ensure that your value is evident to the organization you work for. You need to be able to take initiative and be proactive in the company. Look out for challenges developers might encounter as they use the company’s product and take steps to address them.

Love learning, be curious
As a DevRel advocate, you need to be open to learning as the company’s product evolves. You need to be willing to learn, do your research, make comparisons, ask questions, and always think of ways you can make the product better and the job easier for developers.

Good verbal and written communication skills
DevRel involves a lot of writing, documentation, content creation, and speaking. You need to be able to communicate well with your audience and to do this, you need to first identify your audience and know the language that they speak. For example, it would be ineffective to write documentation in English without taking into account other non-English speaking audiences that might want to access that documentation. You need to be a strong communicator and be able to explain technical concepts to a variety of audiences. Some people assimilate things better when they watch videos, while some assimilate better when they read documentation, articles, etc. You need to be able to cater to your various audiences’ needs and communicate with them through the platform they’ll understand.

Problem Solving
This involves adopting an innovative mindset and thinking creatively to address challenges that may emerge. Instead of relying on conventional or routine approaches, you should be able to think outside the box to solve issues that may arise.

Organizational skills
This is a crucial skill needed to work in DevRel. Your responsibilities often include coordinating events, conferences, and talks, therefore time management is essential, as it enables you to allocate resources efficiently and meet deadlines. You need to set clear goals to help you prioritize tasks and stay focused on key objectives. Paying attention to detail is also important as it ensures the quality of your work and prevents oversights that could impact results.

Empathy
DevRel requires the ability to resonate with the challenges, concerns, and experiences of your audience. You need to be able to feel the plight of your audience and relate with them. You need to be sensitive to the diverse perspectives and backgrounds of your audience, recognizing that individuals may approach technology and development with varying levels of experience and understanding. You should be open-minded and receptive to various ways of approaching problems or solutions in order to connect with a broad audience and cater to their diverse needs. Be always ready to teach your audience what they don’t know. Be willing to share your knowledge with others.

Do I Need to be a Developer to work in DevRel?

This topic sparks controversy in the DevRel community, with some staunchly advocating the necessity of being a developer for a DevRel role. However, in my opinion, no, you do not necessarily need to be a developer to work in DevRel. Yet, this varies based on the specific role, as not all DevRel jobs require you to have a strong knowledge or background in development.

DevRel has a lot of writing, content creation and speaking involved. Some roles are more technical than others. For example, a community manager might not need to have as much technical expertise as a DevEx Engineer. So before pursuing a career in DevRel, you need to identify your goals and preferences and decide what areas you’d like to work in.

DevRel encompasses a range of roles, thereby providing diverse job opportunities. Aside from the job roles earlier mentioned, roles like Social Media Manager, Technical Writer, and Content Creator are available, spanning product, marketing, and customer-facing aspects of DevRel. But if you know you have a knack for coding and enjoy teaching, then a DevEx engineer or Developer advocate may be more suitable.

In choosing DevRel as a career, building trust is fundamental and to do this you need to ensure that you’re honest, reliable, and consistent in your actions. Do not put misleading messages out there or promote questionable brands.
Have a passion for your work, approach issues with an open mind, and always be open to learning more about your product, community, audience, and all that the job entails.

Developer Relations is a rewarding field and depending on your position you have the opportunity to educate, share your knowledge, create content, write blog posts and articles, write documentation, organize events, speak at events and conferences, manage communities and the list goes on. So if you possess the aforementioned skills and have a genuine passion for development and the developer community, then you should consider a job in DevRel.

Do you have more questions about DevRel? Leave a comment in the comment section.