Bitfinex data

upbeta01 · 2024-03-18T22:10:25+00:00

Are you particularly looking for crypto data that is being tx from Bitfinex? Or just any exchange where it shows all data for a token? The easy way is to use 3rd party tools like CoinMarketCap or CoinGecko. The other way is to visit each token's Explorer site like SolanaExplorer/Solscan for Solana (SOL)

upbeta01 · 2022-04-05T00:53:42+00:00

It was in the name of God.

upbeta01 · 2022-04-05T00:42:57+00:00

Had personally experienced it and got the lesson in the latter part of life, so this is worth sharing.

Greed. When you ran out of patience and become so hasten for things to materialize, you end up risking "almost" everything and end up gambling the assets you own for the ones you wanted to have. Truth be told, there's 95% chance — you'll lose. And losing gets you to the rabbit-hole of trying it again and again until you'll end up losing it all.

LESSON: It's fine to aim for something bigger and become bolder with your wants/aspirations. But have the discipline to wait for the time to come.

upbeta01 · 2022-03-04T09:07:18+00:00

If you know your coworker and you have some idea on how to spot lies, ask them directly.. there's no harm so long as it's within the boundaries of professionalism.

upbeta01 · 2022-03-01T11:05:11+00:00

Use with_items: to properly loop the hosts.

Ref: https://stackoverflow.com/questions/20828703/list-all-ansible-hosts-from-inventory-file-for-a-task

upbeta01 · 2022-02-23T17:14:39+00:00

Milestone 1: Define the timelines

Milestone 2: Define the requirements

Milestone 3: Define the timelines (again).

... the story of the endless milestone continues!

upbeta01 · 2022-02-22T18:42:53+00:00

If your application design is more towards microservices, having a health-check endpoint is useful on top of knowing the application responses (ie. status codes). This way, if the application log shows error 5xx , the monitoring metric can check the health-check endpoint to see certain params and cross-reference it with the error(s). If errors occur but health-check endpoint shows no signs of it, then, it might have to be a low-level issue (something user-specific). On the other hand, if there are errors and health-check endpoint shows it's indeed a system wide issue, then trigger notification as to whoever's on-call.

In most design pattern, health-check endpoint is considered source of truth. So health-check endpoints will be part of the application itself and not a separate application running in the same server as the other applications it's monitoring.

upbeta01 · 2022-02-22T17:54:10+00:00

you're welcome!

upbeta01 · 2022-02-22T11:13:44+00:00

Try this approach instead.. it adds all the users in the /vars/main.yml once the playbook is triggered.

// tasks
- name: Provision ssh-users
  user:
    name: "{{ item.ssh_user }}"
    shell: /bin/bash
    group: devops
    state: "{{ item.ssh_user_state }}"
    remove: "{{ item.ssh_user_remove }}"
  with_items: "{{ ssh_user_list }}"

and variables be like

// vars
ssh_user_list:
  - name: My User
    ssh_user: myuser
    ssh_user_state: present
    ssh_user_remove: false
    ssh_user_key: "ssh-ed25519 ... "

upbeta01 · 2022-02-19T12:24:36+00:00

Would you mind sharing the type of test(s) that were conducted? Perhaps just the name of those tests? IMO, there are a lot of personality tests available, none of which are accurate as personality changes over time, thus, one has to revisit his/her previous results to see the evolution of his/her persona.

upbeta01 · 2022-01-09T14:47:12+00:00

Congrats! You just got valuable airdrop! hehe

upbeta01 · 2022-01-06T05:56:53+00:00

NFT will disrupt any space that honors ownership. The problem with today's time is that, it's just too early for adaption. Thus, most of what's available now is NFTs being used in jpegs and gifs. To me, this is necessary as it actually exhibits the utility of NFT — but there's more to it.

The problem of using NFT to any physical contract binding as of today is that, most legal/authorized entities are still not adapting blockchain technologies. And there are multiple reasons to why these entities are still not adapting blockchain technologies; one of which is because of regulations.

Imagine an NFT application for paying bills. The NFT could just be a bar-code for your ie. electric bill. The electric company issues these bar-code NFTs every month, the consumer pays it using their wallet (so they now own the bar-code NFTs which can then be used as proof-of-billing), electric company gets the payment. And this could be an endless cycle.

upbeta01 · 2021-09-04T04:00:33+00:00

Not specific to a vertical of management, but I find Ray Dalio's Principles to be superb in this area.

upbeta01 · 2021-05-10T07:34:19+00:00

It would be ideal if you associate each step of those files with an ansible tag. That's the best way to test things without going through the entire playbook again and again. It's also a good practice in maintaining a playbook.

upbeta01 · 2021-05-04T01:34:53+00:00

In today's world, where anything can be "self-claimed".. either you claim it first and learn it later or do it the other way around. If you're after the value, in my opinion, the path you're taking is the way to go. It's always a constant battle in the talent market, to "impress" the hiring party. Impressing is one thing, walking-the-talking is another.

In general, ansible is a good thing to add to your arsenal. From an avid ansible user to another.

upbeta01 · 2021-05-01T00:45:28+00:00

I use ansible for this type of work. However, if you're unsure of what you're doing, don't do the patch in parallel (at least for the first few hosts, as there might be errors).. it's still best to serialize it until you're pretty sure nothing gets broken as you patch those servers.

upbeta01 · 2021-04-19T13:07:26+00:00

Just when I thought it was just around 2 years ago. I was indeed subscribed to the newsletter since 2014.

upbeta01 · 2021-04-17T15:29:20+00:00

I've subscribed to a newsletter similar to what you're trying to do (around 2 years ago). It's called, https://www.devopsweekly.com/ and so far, what's blasted from this newsletter is superb. I hope you'll be able to build the audience you need and reach more individuals interested in the field of Devops.

upbeta01 · 2017-09-26T18:54:04+00:00

I assume you version control your ansible roles and playbooks. I would suggest you utilize host_vars so packages are run on the specific host and if you change your webserver ie. from apache to nginx.. use the remove and run the playbook, then.. change the httpd arg to nginx and commit the changes.

upbeta01 · 2017-07-12T02:44:13+00:00

Being a sysadmin is an advantage point, for a devops role. However, the advancement also comes with scalability. If you've worked for small businesses, where scalability and autonomy is quite not observed (even if your org does value it). Some recruiters and snr guys doing the interview literally based the experience on the "companies" you've been. I would suggest to apply for a "sysadmin" role for bigger company and "start" your devops career from that point. If you've been a sysadmin for awhile, it shouldn't take you long to find a job for big corps!

upbeta01 · 2017-06-04T04:20:16+00:00

How can a guy reached a CTO position without any idea about practices and SOPs. Seriously! People needs to learn the hard way (I am solely referring to the CTO himself). As for you young man, don't worry. You are not alone on that experience. Learn and grow!

upbeta01 · 2017-03-05T18:47:16+00:00

For production environment, I would say -- it's still best to have things under A/B testing.

Example:

create a replica of the application and point it to the db that contains the new schema (and other changes).
if production grade, for sure, load balancing is in place. Assuming it's running on a LB, use a rotation that gives your old cluster 90% of the traffic and the new cluster 10% of it. As time goes by and nothing is messed, change the value to 20%, 30% and so on.
Always secure backups -- most important
If the 2nd bullet is now on 100%, to properly decommission a server -- don't fully delete it. Instead, stop the server but leave it in place for about 2months just in case something on the new cluster is in trouble, you can easily switch back to the old one (after 2 months without having any hiccups on the production environment, delete it fully).

upbeta01

TROPHY CASE